Versioning

Two things have versions: each product's scripts, numbered like 1.3.0, and the API they call, dated like 2026-12.

Script versions

Each product's scripts are in their own folder on this site. For the Storefront:

• /storefront/v1/ is what most sites should use. Fixes and new features in 1.x reach your visitors within minutes of a release, and nothing in a 1.x release breaks what worked before.
• /storefront/1.3.0/ never changes. Use it, with integrity hashes, when you need to know exactly which code runs on your site; you then upgrade by hand.
• The scripts of one release are built together and always carry the same version.
• Each release folder also holds its source maps (*.map), its TypeScript declarations (types/) and integrity.json.
• Version numbers follow semantic versioning: a patch release (1.0.1) fixes, a minor release (1.1.0) adds, and anything that would break a working site waits for a new major version, served from its own /storefront/v2/ while /storefront/v1/ keeps working.

API versions

Each API is versioned by date. The Storefront API's first version is 2026-12, and it's in every request path (/storefront-api/2026-12/…).

• A released version only gains fields. New optional fields can appear, so ignore the ones you don't know; nothing is renamed, retyped or removed.
• Anything breaking ships as a new version, beside the old one.
• Each API version is supported for at least 12 months from its release.
• The scripts pin the API version they were built for: storefront.js 1.3.0 speaks 2026-12 unless you pass apiVersion. A pinned script keeps working for as long as its API version is supported.

Supported environments

What's new

Each product's changelog lists its releases: the Storefront changelog.