Skip to content

fix(ci): make RC publication resumable - #20

Merged
MarcStdt merged 2 commits into
mainfrom
codex/npm-release-auth
Oct 28, 2026
Merged

MarcStdt merged 2 commits into
mainfrom
codex/npm-release-auth

Conversation

@MarcStdt

@MarcStdt MarcStdt commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Changes

  • Pass the existing NPM_TOKEN to the complete publication step.
  • Wait for npm client metadata after bootstrap: npm accepts uploads before the metadata used by Changesets becomes visible.
  • Allow manual publication of an existing RC tag; an empty input retains authentication-only preflight.
  • Keep next-only RC validation and package contents unchanged.

Verification

  • Workflow YAML parses and git diff --check passes.
  • The actual release reproduced the metadata race: client upload succeeded, then Changesets immediately received E404 and tried publishing it again. Other packages became visible after processing.
  • Full SDK CI must pass before merge; retry the existing v4.0.0-rc.1 tag afterward.

No stable-tag promotion or package version changes.

The token was scoped to client bootstrap, leaving the Changesets step without publication credentials. Allow an explicit existing RC tag on manual dispatch so failed releases can resume without moving tags.
npm accepts the first client publish before its registry metadata is readable. Changesets otherwise tries publishing it again immediately and fails. Wait for visibility before continuing the release.
@MarcStdt MarcStdt changed the title fix(ci): authenticate complete RC publication fix(ci): make RC publication resumable Oct 28, 2026
@MarcStdt MarcStdt closed this Oct 28, 2026
@MarcStdt
MarcStdt merged commit 5a3bac5 into main Oct 28, 2026
4 checks passed
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