Repository navigation
docs: the release tag does not publish the crate - #5
Merged
Merged
Conversation
The cmduse-v* tag builds the six assets and stops; cargo publish is a separate step, and verify-crate fails "absent from the index" until it runs. A green release run reads as a finished release otherwise.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
JeffreyJYZ
approved these changes
Nov 5, 2026
This branch was successfully deployed
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.
One rule for the memory file, learned while shipping 0.7.31: the
cmduse-v*tag builds the six release assets and stops.cargo publish -p cmd-usageis a separate step, so a green release run is not a finished release —verify-crate.tsreported0.7.31 absent from the indexfor 40 polls until the crate was published by hand.No code change.