fix(ci): make npm-publish idempotent (skip already-published versions)#4870
Merged
Conversation
At v0.5.1151 a transient artifact digest-mismatch killed npm-publish after @perryts/perry-darwin-arm64 and -darwin-x64 had published; every re-run then died on the first loop iteration with "You cannot publish over the previously published versions", so the remaining five platform packages and the @perryts/perry wrapper could never go out (run 27239815088). Check the registry per package and skip versions that are already there — re-runs and the workflow_dispatch publish_npm=true recovery path now converge instead of hard-failing.
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.
At v0.5.1151, a transient artifact digest-mismatch killed
npm-publishafter the two darwin packages had published. Every re-run then died on loop iteration 1 with:…so
@perryts/perry-linux-*,-win32-x64, and the@perryts/perrywrapper can never publish from re-runs of the tag run (run 27239815088, 2 failures).Fix:
npm view name@verper package and skip versions already on the registry — both for the platform loop and the wrapper. Re-runs and theworkflow_dispatch publish_npm=truerecovery path now converge.After merge I'll dispatch
release-packages.ymlon main withpublish_npm=trueto publish the six missing 0.5.1151 packages.