ci(publish): NPM_TOKEN bootstrap for first publish, OIDC after - #43
Merged
Conversation
Verified against npm docs: trusted publishing can only be configured AFTER a package exists (both the web UI and `npm trust` require it), so a brand-new package's first publish cannot use OIDC — it needs a token once. The publish job uses an NPM_TOKEN secret when present (first release) and falls through to OIDC when absent (every release after the trusted-publisher record is set + the secret deleted). README documents the 3-step bootstrap. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Corrects #42. I verified the npm constraint against the docs and it changes the answer.
The constraint (verified)
npm trusted publishing (OIDC) can only be configured after a package already exists — both the web UI and the
npm trustCLI require it (npm/cli#8544). So the first publish of a brand-newgithub-wardencannot use OIDC — it needs a token exactly once. Pure-OIDC (#42) would fail the inaugural publish.Fix
The
publishjob now does token-bootstrap → OIDC-forever:NPM_TOKENsecret present → writes.npmrcand publishes with it (the one-time bootstrap).Both paths keep
--provenanceand the idempotency skip.The bootstrap (3 steps, documented in the README)
NPM_TOKENrepo/org secret (npm granular token, publish scope) →just release minor→ publishes0.2.0, creating the package.npm trust github github-warden --repo=intentius/github-warden --file=publish.yml --allow-publish(or the npm web UI).NPM_TOKENsecret — futurejust releaseruns are token-free OIDC.Verification
publish.ymlvalid YAML; publish step passesbash -n.🤖 Generated with Claude Code