fix(version): every dev default tells the truth, and the channel classifies the bundle - #64
Merged
Merged
Conversation
…sifies the bundle The released line is 0.8.0, yet an unstamped gds claimed a released 0.7.0, the controller claimed 0.4.0-dev, and development bundles were stamped 0.4.0-dev forever. All three defaults move to 0.8.0-dev: a dev build can never masquerade as a release, and a development bundle is dated to the line it came from. The bundle classifier had a sharper defect: provenance treated a lock as released unless its version equalled the CURRENT DevelopmentBundleVersion, so bumping that constant would have silently reclassified every not-yet-regenerated development lock as released and skipped its source verification. The channel field alone classifies now; an older dev version is still a development bundle and is verified as one. Goldens and the repository's own lock are regenerated at 0.8.0-dev. Claude-Session: https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF
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
1 participant
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.
The released line is 0.8.0 (gds-v0.8.0, 2026-08-30), yet an unstamped
gdsclaimed a released 0.7.0,gds-controllerclaimed 0.4.0-dev, and development bundles were stamped 0.4.0-dev forever. All three dev defaults move to0.8.0-dev— an unstamped binary can never masquerade as a release, and a development bundle is dated to the line it came from.The sharper defect: provenance classified a lock as released unless its version equalled the current
DevelopmentBundleVersion, so bumping the constant would have silently reclassified every not-yet-regenerated development lock as released and skipped its source verification — the opposite of what a version bump should do. The channel field alone classifies now; an older dev version is still a development bundle and is verified as one (transition-safe for every policy-owner repo).Goldens and the repository's own lock regenerated at 0.8.0-dev through the generate ceremony on the committed tree.
validate_go_core.sh: PASS (full).https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF