Don't use force in cargo publish. - #100
Merged
Merged
Conversation
It's not clear why it was there in the first place, but we do know now that it prevents us from restarting the publishes that failed after some crates have been published (e.g. due to spurious crates io issues). Due to the `force` flag we try to re-publish an already existing crate, which is not allowed and results in the publish process abort.
There was a problem hiding this comment.
Pull request overview
Updates the Rust publishing GitHub Actions workflow to avoid forcing re-publishes, enabling safe re-runs when a previous publish partially succeeded (e.g., crates.io transient failures).
Changes:
- Remove
--force '*'fromcargo workspaces publishinvocation to prevent attempts to re-publish already-published crates.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
satyamz
approved these changes
Apr 7, 2026
dmkozh
enabled auto-merge (squash)
April 7, 2026 15:38
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.
It's not clear why it was there in the first place, but we do know now that it prevents us from restarting the publishes that failed after some crates have been published (e.g. due to spurious crates io issues). Due to the
forceflag we try to re-publish an already existing crate, which is not allowed and results in the publish process abort.