CalVer Release Process
This project uses Calendar Versioning with the format YYYY.0M.MICRO.
Version Format
code
YYYY.0M.MICRO
- •
YYYY— Full year (e.g.,2026) - •
0M— Zero-padded month (e.g.,02for February) - •
MICRO— Incremental patch number within the month, starting at0
Examples
| Version | Meaning |
|---|---|
2026.02.0 | First release of February 2026 |
2026.02.1 | Second release of February 2026 |
2026.03.0 | First release of March 2026 |
Release Steps
- •Ensure all CI checks pass on
main. - •Update
CHANGELOG.md: move items from[Unreleased]to a new version header. - •Update
versioninpackage.jsonto the new CalVer version. - •Commit:
chore: release YYYY.0M.MICRO - •Tag:
git tag vYYYY.0M.MICRO - •Push tag:
git push origin vYYYY.0M.MICRO
CHANGELOG Format
Follow Keep a Changelog:
markdown
## [YYYY.0M.MICRO] — YYYY-MM-DD ### Added - ... ### Changed - ... ### Fixed - ...