Skip to content

ci: use npm trusted publishing #11

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
vndv merged 1 commit into from
May 30, 2026
Merged

ci: use npm trusted publishing #11

Show file tree
Hide file tree
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
1 change: 0 additions & 1 deletion .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,4 +37,3 @@ jobs:
title: "chore: version packages"
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -254,7 +254,7 @@ npm run version-packages
npm run publish-packages
```

The workflow publishes with the `NPM_TOKEN` repository secret. Use npm trusted publishing later if you want tokenless provenance publishing.
The workflow uses npm trusted publishing through GitHub Actions OIDC.

Local release commands are still available when needed:

Expand All @@ -263,7 +263,7 @@ npm run ci
npm run local-release
```

GitHub Actions needs `NPM_TOKEN` as a repository secret, or npm trusted publishing configured for `.github/workflows/publish.yml`.
GitHub Actions needs npm trusted publishing configured for `.github/workflows/publish.yml`.

---

Expand Down
Loading