chore: Fix cargo-mono publish command#94
Merged
Conversation
kdy1
changed the title
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.
What changed
Removed the obsolete
--no-verifyflag from thecargo mono publishstep in the publish workflow.Why
After updating to
cargo-mono@0.6.9, the publish job failed because the new CLI no longer accepts--no-verify:cargo-mono 0.6.9now documents that delegated Cargo verification remains disabled for the publish dry-run path, so the old flag is no longer needed.Validation
26939632822, job79478329256.cargo mono publish --helpforcargo-mono 0.6.9no longer lists--no-verify.cargo mono publish --dry-runsuccessfully on a clean working tree.git diff --check HEAD~1..HEAD.