Repository navigation
Add a workflow to yank a crates.io version - #10
Merged
Merged
Conversation
bootintel-cli 0.4.1 needs yanking: the crate was renamed to bootintel and until that old name is yanked, two names install a working `bootintel`, which is the exact ambiguity the rename removed. It could not be done from this machine. The registry token lives only as a repository secret, which is where a publish credential belongs, and GitHub secrets cannot be read back, only used inside Actions. So the yank runs where the publish ran, with the same secret. workflow_dispatch only, no defaults, so it cannot fire by accident. It takes a reason for the run log, and refuses a version that is not on the registry so a typo fails before reaching crates.io. Unyank is the same workflow with the action flipped, because yanking is reversible where publishing is not. 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.
bootintel-cli0.4.1 needs yanking. The crate was renamed tobootintel, and until the old name is yanked, two names install a workingbootintelbinary, which is the ambiguity the rename existed to remove.It cannot be done from a laptop. The registry token lives only as a repository secret, which is where a publish credential belongs, and GitHub secrets cannot be read back, only used inside Actions. So the yank runs where the publish ran, with the same secret.
workflow_dispatchonly, with no defaults, so it cannot fire by accident. Takes a reason for the run log, and refuses a version that is not on the registry so a typo fails before reaching crates.io. Unyank is the same workflow with the action flipped, because yanking is reversible where publishing is not.Documented in
docs/releasing.md.