Uh oh!
There was an error while loading. Please reload this page.
chore: declare next release in VERSION (0.10.1) for the release train - #417
Merged
Conversation
The train reads this file to cut tags: vX.Y.Z-rc.N on every staging promotion (pre-release binaries for FR; 'latest' never sees them) and vX.Y.Z on the prod promotion. The binary's own version still derives from the tag at build time (release.yml ldflags) -- this file only declares intent, uniform with tracebloc-py-package's pyproject version. 0.10.1 ships the cosign identity anchor fix (#415). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
LukasWodka
commented
Jul 28, 2026
ContributorAuthor
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 5697338. Configure here.
saadqbal
previously approved these changes
Jul 28, 2026
Two guards raised in release-train review: (1) any tag's base X.Y.Z must match the VERSION file (train-cut or manual), so the file can never go silently stale after an out-of-train release; pre-VERSION tags are grandfathered for rebuilds. (2) STRICT stability: only plain vX.Y.Z is a stable release -- rc tags AND malformed variants (v1.2.3rc1, no dash) are prereleases, so 'releases/latest' (the installer bootstrap) can only ever resolve a real production build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
saadqbal
approved these changes
Jul 28, 2026
Uh oh!
There was an error while loading. Please reload this page.
LukasWodka
commented
Jul 29, 2026
ContributorAuthor
/fr-pass |
4 tasks
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
VERSIONfile declaring the next release:0.10.1(ships the cosign identity-anchor fixfix(install): anchor cosign identity to version tags (D29, #1269 row 4) #415, currently unreleased on develop).vX.Y.Ztag is a stable release; rc tags and malformed variants (v0.11.0rc1, no dash) are marked prerelease, soreleases/latest— what the installer bootstrap resolves — can only ever serve a real production build.How releases work now
Train staging hop → merges develop→staging + tags
v0.10.1-rc.1→ signed pre-release binaries for FR (invisible tolatest). Train prod hop → merges staging→main + tagsv0.10.1→ stable release, becomeslatest. Manual tagging by release-managers still works — the guards just keep it honest.Convention
Bump
VERSIONon develop when the next cycle's content is decided. The train refuses rc/final tags for an already-released or regressed version.🤖 Generated with Claude Code