fix: preserve publish checksums across staged retries#61
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.
Post-release hardening for the checksum limitation exposed while auditing 0.7.5.\n\nThe publisher now packages normally first, falls back to local patches only for the expected missing exact-version registry dependency, and refreshes each checksum from a normal archive on every publish attempt. This preserves checksum-matched prefix recovery after a partial staged publication.\n\nFocused evidence:\n- publisher unit module: 6 passed\n- exact 19-crate post-publication checksum audit: 19/19 matched\n- 0.7.5 was already published successfully before this post-release change; this PR does not move its tag