docs: bump GHA recipe semvertag floor to >=0.3#6
Merged
Conversation
The 0.2.x line predates the GitHub provider; >=0.2 in the GHA recipe silently misleads users into thinking 0.2.0 supports GitHub. Tighten the floor to >=0.3,<1 in the three GHA examples (README hero + docs/providers/github.md Quick Start + strategy example). GitLab CI's >=0.1,<1 floor stays as-is — 0.1.x is the correct floor for that provider. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Summary
Tightens the
uvx 'semvertag>=...,<1'floor from0.2to0.3in the three GitHub Actions recipe snippets. 0.2.x doesn't have the GitHub provider — anyone copying the recipe expecting it to work on 0.2.x would get a confusing 401 because no provider could be resolved.GitLab's
>=0.1,<1floor stays — 0.1.x is correct for that provider.Also serves as the next dogfood: this PR's source branch is
bugfix/..., so the dogfood workflow should auto-tagmainwith0.3.1on merge.Test plan
bugfix/prefix, computespatchbump, creates tag0.3.1gh release listshows the new tag (no GitHub release yet — that's intentional, publish.yml fires on release creation only)🤖 Generated with Claude Code