Repository navigation
fix: retry sibling publish and poll npm in release verify - #10179
Merged
Merged
Conversation
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
Contributor
davidkaplanbitgo
approved these changes
Nov 13, 2026
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.
Make the stable npm release tolerate transient publish failures and npm propagation lag, so first runs stop needing a recovery-mode rerun.
Publish siblings (pass 1)now retrieslerna publish from-packageup to 3 times, 60s apart.package.jsonfiles lerna rewrote, so the next attempt doesn't fail withEUNCOMMIT.Verify recovery published the missing versionstoVerify published versions are on npm, and run it on every non-dry-run release instead of only in recovery mode.bitgo.curlnetwork error in the verify step now counts as "not visible yet" instead of aborting the step.bitgopublish) and versions npm holds in a staged state still need a recovery run.Ticket: WCN-4679