Releases

We use changesets for automated releases.

Changesets

• Every pull request that modifies production code (not examples/docs) must include a changeset.
• By default, use patch (non-breaking).
• To override, apply the minor or major label (CI enforces patch otherwise).

Regular Releases

• The Changesets action automatically creates a Version Packages PR.
• Merging this PR triggers the release workflow, which publishes the npm packages.

Maintenance Releases

• Enable the release workflow on the maintenance branch.
• Only patch releases are allowed.
• To release:
  1. Create a pull request against the maintenance branch.
  2. Merge it to trigger the release workflow.

Beta / Pre-Release Cycle

For starting and managing a major-version pre-release cycle (beta releases on main while maintaining stable patches), see Pre-Release Cycle.

Quick reference:

• Enter beta mode: pnpm changeset pre enter beta
• Exit beta mode: pnpm changeset pre exit
• Backport fixes: add the backport label to the merged PR