fix: package unpublished release dependencies locally#60
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
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.
Fix the 0.7.5 publisher preflight exposed by tag run 29937298640. Cargo packaging now receives local crates.io patches for every publishable workspace crate, allowing exact-version internal dependencies to resolve before those versions exist in the registry while preserving registry dependencies in packaged manifests.\n\nFocused validation:\n- regression test failed before the fix and passes after it\n- complete publish-release unit module passes (6 tests)\n- exact failed command now packages all 19 release crates successfully\n- no crates were published by the failed tag run