fix(ci): retry alpha dist-tag verification on registry propagation delay - #83
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 repair workflow successfully set alpha dist-tags and pushed git tags, but failed because
npm viewimmediately read stale dist-tag data. This patch adds retry polling to both alpha dist-tag verification steps so they wait for registry propagation before failing.Changes:
publish-alpha.ymlandrepair-alpha-metadata.ymlnow retry up to 25 times (~5 min at 10-15s sleep intervals)--prefer-onlineflag with a fallback to plainnpm viewResolves the race where npm's CDN hasn't propagated the newly-set dist-tag.