Stripe Formalizes a Continuous API-Versioning Cadence
Twice-yearly major versions are now paired with monthly backward-compatible releases carrying the same version name.
Stripe restructured how it names and ships API versions in 2026, moving to a cadence that combines twice-yearly major releases with monthly incremental ones. A major release, issued twice a year, is the only kind allowed to include changes that aren't backward-compatible with the previous version. Every monthly release in between carries only backward-compatible changes and keeps the same version name as the most recent major release, distinguished by its date stamp.
In practice, that means a version identifier like `2026-07-29.dahlia` tells a developer two things at once: the `dahlia` name identifies which major version family the release belongs to, and the date identifies exactly which monthly snapshot of that family they're integrating against. Throughout 2026, the `dahlia` family moved through dated releases in March, April, May, June, and July, with `clover` as the prior major version before it.
For teams integrating with Stripe, the practical effect is that pinning to a specific dated version — as Stripe's documentation recommends — guarantees a fixed, unchanging contract, while newly created API keys default to the latest dated release of the current major version. Upgrading between monthly releases within the same major version should never require a breaking change on the integrating side, since Stripe reserves breaking changes for the twice-yearly major bumps.
The approach sits between two more common models: a single, ever-changing "latest" API that can break integrations without warning, and infrequent major-version bumps that force large migrations all at once. Stripe's dated, backward-compatible monthly releases let an integration benefit from new functionality continuously while still treating any breaking change as an explicit, opt-in upgrade tied to one of the two yearly major versions.
Stripe's own API versioning documentation is the canonical, continuously updated reference for the current version name, the full history of prior versions, and the process for upgrading an integration from one major version to the next.