Repository navigation
ci: raise the semvertag floor to 0.10.0 in the wrappers and docs - #100
Merged
Merged
Conversation
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.
The GitHub Action and the GitLab component pinned
semvertag>=0.5.0,<1, and the GitLab and index quick-start snippets pinned>=0.1,<1. The docs now describe behaviour that only exists from 0.9.0 (v-prefixed tags, #93) and 0.10.0 (the decline statuses, #98). A fresh runner resolves the latest release anyway, but a floor that low lets a cached older version silently skip both.Every
uvx 'semvertag…'pin inaction.yml,templates/semvertag.yml, README,docs/index.mdand both provider guides is now>=0.10.0,<1. The GitLab dry-run section no longer tells readers to raise the floor for--dry-run, since the quick-start floor already covers it.The descriptor gate's own minimum stays at 0.5.0: it guards "the floor supports
--dry-run", which>=0.10.0satisfies. Its below-floor fixture built the bad template by replacing>=0.5.0in the shipped one; that now replaces>=0.10.0, or it would match nothing and stop testing anything.Verified with
just lint-ci,just test-ci(500 passed, 100% coverage),just adr-checkandjust docs-build.