Skip to content

fix: wait for npm publication visibility before verification - #52

Merged
omermorad merged 3 commits into
nextfrom
fix/npm-publication-visibility
Oct 31, 2026
Merged

omermorad merged 3 commits into
nextfrom
fix/npm-publication-visibility

Conversation

@omermorad

@omermorad omermorad commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Publishing can succeed while npm still returns E404 for the new version. Run 41223628865 uploaded all seven packages successfully but failed its immediate verification; the packages then became visible over the following five minutes.

Wait up to ten minutes across the batch for newly published versions, their beta tags, and downloadable tarballs to appear, refreshing registry metadata every ten seconds. Retries only read metadata and download tarballs with lifecycle scripts disabled. Wrong package identities/source commits, changes to preserved versions, and errors other than E404 still fail immediately. Document this behavior in RELEASING.md.

Validation: pnpm build, pnpm lint, pnpm test (14 passed), pnpm test:e2e (361 passed, 1 skipped), actionlint, and targeted shell regression checks covering delayed version/tag/tarball visibility, timeout, authentication/server errors, immutable versions, and preserved distribution tags. Live verification passed for all seven published packages, including package identity, source commit, beta tag, and tarball download. The last tarball became downloadable roughly ten minutes after npm accepted the upload. Rerun 41223628865 passed with all uploads skipped.

@omermorad
omermorad merged commit edf0b41 into next Oct 31, 2026
11 checks passed
@omermorad
omermorad deleted the fix/npm-publication-visibility branch October 31, 2026 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant