Skip to content

Publish with Trusted Publishing only - #5

Merged
Inchill merged 1 commit into
mainfrom
ci/trusted-publishing-only
Oct 22, 2026
Merged

Inchill merged 1 commit into
mainfrom
ci/trusted-publishing-only

Conversation

@Inchill

@Inchill Inchill commented Oct 22, 2026

Copy link
Copy Markdown
Owner

Moves the release back to npm Trusted Publishing only. 1.1.1 was published with a temporary NPM_TOKEN after Trusted Publishing attempts failed with 503; that token is no longer meant to be used.

Changes

  • The publish step no longer sets NODE_AUTH_TOKEN from secrets.NPM_TOKEN, so a leftover secret cannot take over authentication.
  • The workflow header now describes the Trusted Publisher setup on npmjs.com (user Inchill, repository react-whiteboard, workflow release.yml, no environment, npm publish and npm dist-tag allowed) and npm's rule that a new connection expires if it has not published within 48 hours.
  • The 20-minute timeout and verbose publish log stay, so the next Trusted Publishing release shows clearly whether the earlier 503 is gone.

No version change, so merging this does not publish anything.

Setup outside the repository

  • Revoke the granular token on npmjs.com and delete the NPM_TOKEN repository secret.
  • Create the Trusted Publisher connection shortly before the next release.

Generated by Claude Code

The release no longer reads an NPM_TOKEN secret, so npm always authenticates
through Trusted Publishing. The header describes the npmjs.com setup and the
48-hour window a new connection has to publish before it expires.
@Inchill
Inchill merged commit 8c7b774 into main Oct 22, 2026
1 check 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