Switch to CalVer and bump version to 26.8.0 - #313
Merged
Conversation
Cargo enforces strict SemVer with no leading zeros, so the month is unpadded (2026.8.1, not 2026.08.1). Updates the release process docs to match.
Switches from 2026.8.1 to 26.8.0: YY.M.MICRO with MICRO starting at 0.
nicomiguelino
changed the title
sergey-borovkov
approved these changes
Aug 28, 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.
What
Switches versioning from SemVer to CalVer:
YY.M.MICRO(two-digit year, unpadded month, micro starting at0). First release under the new scheme:26.8.0.Why
Cargo parses
Cargo.toml'sversionas strict SemVer, which rejects leading zeros — confirmed26.08.0failscargo checkwhile26.8.0doesn't. So the month stays unpadded everywhere: Cargo.toml, git tag, and--versionoutput all match.Changes
Cargo.toml,Cargo.lock,action.yml,Dockerfile→26.8.0## Release Processrewritten forYY.M.MICRO, with the leading-zero caveat and how to pick the nextMICRO