Repository navigation
fix(release): wait for npm publication verification - #6
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
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.
The SDK release command could upload a package successfully, then stop the batch because its fixed 15-read verification loop exhausted after roughly 28 seconds. The report left the package as
publishing, and the silent wait looked like a hung upload.Poll fresh registry metadata with a five-minute deadline, bounded exponential backoff, transient-read retries and visible progress. Record successful uploads as
verifyinguntil their SHA-512 integrity is confirmed. Authentication errors and integrity conflicts still stop immediately; uploads are never retried automatically and later packages remain blocked until verification succeeds. Update both release guides with the verification states and pnpm-specific authentication steps.Validation:
pnpm run releasepasses lint, facade checks, build, typecheck, 40 release-script tests plus 128 SDK tests (two existing skips), and all four archive checks. Regression cases cover delayed visibility, cache keys, Retry-After, time limits, transient reads, authentication failures, integrity conflicts and unchanged upload ordering. Read-only checks against npm also verified all four published 2.2.0 tarballs against the prepared SHA-512 values; package contents are unchanged.