Mint a release
Do not publish a release unless the user explicitly asks. Pushing a new version
to main requests publication, so commit and push only on that explicit request.
The complete process, including the per-product version and changelog files, CI
behaviour and recovery, is in docs/releases.md.
Read it first and follow it; this skill only summarises the preparation.
Prepare
- Set the product's version file to an unused, higher
X.Y.Z. - Move the relevant Unreleased notes in that product's changelog into
## [X.Y.Z] - YYYY-MM-DD. Keep any remaining work under Unreleased. - Use that changelog entry as the release description.
- Run the affected tests and review the changes.
Do not create tags manually or reuse published versions.