v2 changelog

v2 is frozen at 2.13.0. No further v2 releases are planned. All active development happens on the current release (4.0.1).

v2 (frozen)

• Last v2 release: 2.13.0 — the final v2 CDN build, served from https://mapi.mapsted.com/v2.13.0/maps.js. Feature set captured on the legacy v2 API reference page.
• Support posture: end-of-life. No new features and no bug fixes. Security patches only at Mapsted's discretion.
• Removal timeline: v2 CDN hosting remains available while the migration shim (src/migration/shim.ts) is still shipped. The shim is scheduled for removal in a future major release, alongside any remaining v2-era aliases.

v3 and onward

All changes for v3 and the current release are tracked on the current docs site:

• Current changelog (4.0.1): /reference/changelog — curated, migration-focused.
• v3 archive: /v3/changelog — historical v3 release notes.
• Repository root: CHANGELOG.md — the authoritative Keep a Changelog file, updated on every release commit.

Release summary:

• v3.0.0 — ground-up TypeScript rewrite, npm distribution, tsup build pipeline. v2 method names were preserved as the canonical public API.

• 4.0.1 — 10 method renames (see table below), MapstedError + 34 structured error codes, origin-validated postMessage via SecurityConfig, typed on/off/once event API, async init() → MapInstance, PRIVATE_CHILD_ACTION removed (CHL-27), highlightStyle() now always throws MAPSTED-1093 (permanently removed), new APIs (setAccessibilityMode, getState, subscribe, setStrictMode).

  All 10 renames vs. v3:

  v3 name (deprecated)	Current replacement
  initialize	init
  set	init (options moved to InitOptions)
  changeFloorById	navigateToFloorById
  changeFloorByName	navigateToFloorByName
  setMapView	setViewport
  centerOnMapoverlay	centerOnMapOverlay (casing fix)
  setDefaultCustomRoutingConfig	setDefaultRoutingConfig
  changeLanguage	setLanguage
  addEventListener	on
  removeEventListener	off

  All deprecated names remain exported via the migration shim and emit a console.warn on first call (or throw MAPSTED-1093 in strict mode). See the migration guide for the full upgrade checklist.

Why v2 has no per-version changelog here

v2's per-version release notes lived on the legacy distribution server. They are not mirrored into the current docs site because:

1. v2 is frozen. There is nothing to append.
2. The only v2 question that matters going forward is "how do I upgrade?" — answered by the migration guide.
3. Historical v2 surface for lookup is captured on the legacy v2 API reference page.

If you need the historical per-version v2 release notes, keep your pinned copy of the v2 distribution bundle.

Related pages

• Migration guide
• Legacy v2 API reference
• Current changelog (4.0.1)
• v3 archive
• Compatibility notes