docs: describe semver versioning in versions.env [bump:minor]#13
Closed
julian-goldstein wants to merge 1 commit into
Closed
docs: describe semver versioning in versions.env [bump:minor]#13julian-goldstein wants to merge 1 commit into
julian-goldstein wants to merge 1 commit into
Conversation
Demo of the new versioning flow: this build/ change triggers vendor-toolchain on merge, which (unmarked default / explicit [bump:minor]) bumps the highest clean tag v0.5 to v0.6.0. No fingerprinted build input changed, so every tool is reused from the v0.5 release. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
Demo purpose served (v0.6.0/v0.6.1/v0.7.0 cut). The stale-comment fix it carried is folded into #17. |
julian-goldstein
added a commit
that referenced
this pull request
Jun 19, 2026
Folds in the doc fix from the now-redundant demo PR #13. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Demo of the new semver workflow. Updates the now-stale
TOOLCHAIN_VERSIONcomment inbuild/versions.env(it still said "CI bumps it by 0.1").What to watch:
markerscheck runs on this PR and should report a minor bump (subject carries[bump:minor]; it's also the default).build/**change triggersvendor-toolchainonmaster. With no fingerprinted build input changed,detectreuses every tool fromv0.5, then it computesv0.5→v0.6.0and publishes that release.(First real exercise of the bump logic;
v0.5is a legacy 2-component tag read as0.5.0.)