Repository navigation
Fix package preparation on Cargo 1.88 - #7
Merged
Merged
Conversation
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.
The first publication rehearsal passed tests and the registry dry-run, then failed because
cargo package --registryis unstable on Cargo 1.88. Remove that flag from the archive-only command; the manifest still restricts publishing to crates.io andcargo publishstill uses an explicit registry.Add the archive command to the Rust 1.88/stable CI matrix so this compatibility boundary is checked before future merges. Validation: actionlint and a manual publication rehearsal with
publish=false; no registry upload.