docs: point the release-image examples at v1.1.0 - #50
Merged
Conversation
The examples said @v1.0.0 — a tag cut before this workflow existed, so a repo copying them verbatim would fail with "workflow was not found". Point them at the tag that will actually contain the file, so the docs inside v1.1.0 are self-consistent rather than describing a release that cannot work. Co-Authored-By: Claude Opus 5 (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.
Caught immediately after merging the workflow: both usage examples pinned
@v1.0.0, a tag cut beforerelease-image.ymlexisted. A repo copying them would fail withworkflow was not found— the pinning model working exactly as intended, against us.Points them at
v1.1.0, which is cut from this commit, so the docs shipped inside that tag describe something that actually works.