Repository navigation
fix(release): retry TypeScript bump until new CLI is on npm - #598
Merged
Merged
Conversation
The bump-ts-packages job runs seconds after publish-npm, but npm takes about a minute to process a publish and its CDN caches package metadata for up to five minutes. pnpm install --lockfile-only therefore failed with ERR_PNPM_NO_MATCHING_VERSION on the first attempt of every release from 0.9.9 through 0.9.15 and needed a manual re-run. Retry the install every 30s for up to 10 minutes instead.
jcarver989
enabled auto-merge (squash)
October 12, 2026 20:32
jcarver989
disabled auto-merge
October 12, 2026 20:33
jcarver989
enabled auto-merge (squash)
October 12, 2026 20:33
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.
Problem
bump-ts-packagesinrelease.ymlhas failed on the first attempt of every release from 0.9.9 through 0.9.15, and each needed a manual re-run:The job starts about 3 seconds after
publish-npmfinishes, but npm doesn't serve the new version yet. npm takes about a minute to process a publish, and its CDN caches package metadata for up to 5 minutes (cache-control: public, max-age=300).publish-npmdoneFix
Retry
pnpm install --lockfile-onlyevery 30s, up to 20 times (~10 minutes), before failing. Retrying the install itself (rather than polling withnpm viewfirst) checks exactly what fails: npm and pnpm request different forms of the package metadata, which the CDN caches separately.