Release Guardrails¶

APX enforces a set of guardrails during the release workflow to prevent invalid or contradictory releases.

Lifecycle-Version Compatibility¶

APX validates that the declared lifecycle is compatible with the version being released:

Lifecycle	Allowed versions	Rejected versions
`experimental`	Must have `-alpha.*` prerelease	Stable versions, `-beta.`, `-rc.`
`beta`	Must have `-alpha.`, `-beta.`, or `-rc.*` prerelease	Stable versions
`stable`	Must be a stable version (no prerelease)	Any prerelease
`deprecated`	Any version	(none)
`sunset`	Releases are blocked	Any version (unless overridden)

APIs on the v0 line have additional restrictions:

Guardrail	Rule
Lifecycle	Must be `experimental` or `beta`
Stable promotion	Not permitted — graduate to `v1` instead
Breaking changes	Allowed — minor version bump instead of rejection

These restrictions are enforced by apx release prepare and apx release promote.

Lifecycle states must progress forward:

experimental → beta → stable → deprecated → sunset

APX rejects backward transitions (e.g., stable → beta).

Scenario	APX behavior
Breaking change on `v0` line	Allowed — suggests minor version bump
Breaking change on `v1+` prerelease	Allowed with warning
Breaking change on `v1+` stable	Rejected — requires new major line
Breaking change on `deprecated`	Rejected — maintenance only