RELEASE.md

Release process

Branch model

• develop: integration branch
• master: release branch

Versioning

Changesets controls versions and changelog via a “Version Packages” PR.

Do not edit CHANGELOG manually — it is generated by Changesets.

Day-to-day

1. Create a feature/fix branch from develop
2. Make your change
3. If it affects users, run: npx changeset
4. Open PR → develop

Quality Gates (before PR)

Run locally before opening a PR:

1. npm run typecheck
2. npm run lint
3. npm test
4. Optional advanced checks:
   • npm run mutation
   • npm run bench

CI Compatibility Matrix

PR validation runs across:

• Node.js 20 and 22
• Ubuntu and Windows runners

This matrix helps detect runtime and tooling regressions before merge.

Release

1. Automation opens “Version Packages” PR from develop → master
2. Merge it
3. Create/push a tag vX.Y.Z
4. CI publishes to npm (OIDC)