Skip to content

ci: publish to NPM through trusted publishing #399

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
kraenhansen merged 1 commit into from
Aug 11, 2026
+7 −0
Merged

ci: publish to NPM through trusted publishing #399

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
7 changes: 7 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,13 @@ jobs:
name: Release
runs-on: macos-latest
environment: main
# Publishing to NPM happens through trusted publishing, which needs an OIDC
# token. Declaring permissions at all narrows them to exactly what is listed,
# so the two the changesets action already relied on are spelled out too.
permissions:
contents: write # version commits, git tags and GitHub releases
pull-requests: write # the "Version Packages" pull request
id-token: write # NPM trusted publishing
steps:
- uses: actions/checkout@v4
- uses: pnpm/action-setup@v4
Expand Down
Loading