Skip to content

ci: use npm trusted publishing for releases #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sjoerdbeentjes merged 1 commit into from
Jul 14, 2026
Merged

ci: use npm trusted publishing for releases #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ concurrency: release-${{ github.ref }}
permissions:
contents: write # create the version PR / push tags
pull-requests: write # open and update the version PR
id-token: write # npm provenance
id-token: write # OIDC token for npm trusted publishing (+ automatic provenance)

jobs:
release:
Expand All @@ -28,6 +28,10 @@ jobs:
node-version-file: .nvmrc
cache: pnpm

# Trusted publishing (OIDC) needs npm >= 11.5.1; Node 22 ships npm 10.x.
# `changeset publish` shells out to this global npm to publish each package.
- run: npm install -g npm@latest

- run: pnpm install --frozen-lockfile

- name: Create version PR or publish
Expand All @@ -43,7 +47,6 @@ jobs:
commit: 'chore: version packages'
title: 'chore: version packages'
env:
# No NPM_TOKEN: auth is handled by npm trusted publishing via the OIDC
# id-token above, and provenance is generated automatically.
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
NPM_CONFIG_PROVENANCE: true
Loading