Skip to content

ci: npm trusted publishing (OIDC), no NPM_TOKEN#25

Merged
priosshrsth merged 1 commit into
mainfrom
ci/npm-trusted-publishing
Jul 14, 2026
Merged

ci: npm trusted publishing (OIDC), no NPM_TOKEN#25
priosshrsth merged 1 commit into
mainfrom
ci/npm-trusted-publishing

Conversation

@priosshrsth

Copy link
Copy Markdown
Collaborator

Switches the release workflow to npm trusted publishing (OIDC) so no long-lived NPM_TOKEN secret is needed.

Changes

  • Add npm install -g npm@latest — trusted publishing needs npm >= 11.5.1; Node 24 ships an older npm.
  • Remove NODE_AUTH_TOKEN from the publish step — auth now comes from GitHub OIDC (id-token: write was already granted).

Required one-time setup on npmjs.com

Package assembly-kit → Settings → Trusted Publisher → add a GitHub Actions publisher:

  • Repository: madebyoutside/assembly-kit
  • Workflow: release.yml
  • Environment: release

Without that, the publish step fails auth. No repo secret required.

🤖 Generated with Claude Code

Trusted publishing authenticates via GitHub OIDC (id-token: write is
already granted), so no long-lived npm token is needed. Upgrade npm to
>=11.5.1 in CI (Node 24 ships an older npm that lacks OIDC support) and
remove the NODE_AUTH_TOKEN env.

Requires a trusted publisher configured on npmjs.com for this repo +
release.yml + release environment.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@priosshrsth
priosshrsth enabled auto-merge (squash) July 14, 2026 08:21
@priosshrsth
priosshrsth merged commit 127d81f into main Jul 14, 2026
5 checks passed
@priosshrsth
priosshrsth deleted the ci/npm-trusted-publishing branch July 14, 2026 08:21
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