Repository navigation
Handle repeated publication of identical release packages - #3
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 main build passed, but publishing an unchanged 2.0.1 package failed after history cleanup changed its commit identity. Reuse an existing stable release only after checking its tag, all three assets, and every payload file; pin the anonymous updater probe to the verified published commit and manifest digest.
Changed same-version payloads, tampered archives, unexpected files, wrong tags, and prereleases remain rejected without modifying published assets. The runtime and version are unchanged.
Validation: Windows PowerShell 5.1 passed all 11 native test suites, the expected QuickEdit baseline, and the actual package build. New regressions cover identical retries, rewritten history, changed ZIP metadata, changed/tampered payloads, extra entries, wrong tags, and prereleases.