docs(contributing): switch to Calendar Versioning - #76
Merged
Conversation
Use 'git tag -a vX.Y.Z -m "vX.Y.Z"' instead of a bare annotated tag, since git tag -a always opens an editor unless -m or -F is given.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the release instructions for maintainers to ensure tags are created as annotated tags without triggering an interactive editor prompt, aligning the documented process with the repository’s release workflow expectations.
Changes:
- Replace the bare
git tag vX.Y.Zexample with an annotated tag command. - Add
-m "vX.Y.Z"to avoid opening an editor when creating the annotated tag.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
nicomiguelino
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (1)
CONTRIBUTING.md:7
- The scheme is described as
YY.M.PATCH, butYYis also described as a non-zero-padded number. That means it’s not always two digits (e.g., 2007 would become7), so theYYnotation can be slightly misleading. Consider clarifying thatYYis year % 100 expressed as a non-zero-padded number.
This project follows [Calendar Versioning](https://calver.org/) using a `YY.M.PATCH` scheme (e.g. `v26.8.0`), a SemVer-compatible variant of CalVer. npm requires `package.json` versions to be valid [SemVer](https://semver.org/), which disallows leading zeros in numeric identifiers, so `YY` is the last two digits of the year as a non-zero-padded number (e.g. `26` for 2026), `M` is the non-zero-padded month, and `PATCH` resets to `0` for the first release of a given year/month and increments for subsequent releases within that same month. Git tags are always `v`-prefixed (e.g. `v26.8.0`). Pre-release tags use the format `v26.8.0-rc.1`.
salmanfarisvp
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
YY.M.PATCH, e.g.v26.8.0).package.json. It's a docs-only change describing the new versioning scheme; the actual version bump will happen in a separate PR when we cut the next release.