Skip to content

ci: publish to npm with trusted publishing instead of a token #4

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
moulibheemaneti merged 1 commit into from
Nov 11, 2026
Merged

ci: publish to npm with trusted publishing instead of a token #4

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
10 changes: 4 additions & 6 deletions .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,14 +9,14 @@ jobs:
runs-on: ubuntu-latest
permissions:
contents: read
id-token: write # required for npm provenance
id-token: write # lets npm trusted publishing verify this workflow (and sign provenance)
steps:
- uses: actions/checkout@v4

- name: Setup Bun
uses: oven-sh/setup-bun@v2

# setup-node is required so npm can pick up NODE_AUTH_TOKEN for registry auth
# Trusted publishing needs npm 11.5.1 or newer; the current Node LTS ships with it.
- name: Setup Node.js
uses: actions/setup-node@v4
with:
Expand All @@ -34,9 +34,7 @@ jobs:
- name: Test
run: bun test

# No token: npm trusts this workflow through trusted publishing, set up on npmjs.com under
# the package's Settings → Trusted publishing (GitHub Actions, moulibheemaneti/docfold, publish.yml).
- name: Publish to npm
run: npm publish --provenance --access public
env:
# NPM_TOKEN: generate an Automation token at npmjs.com → Profile → Access Tokens,
# then add it as a repository secret at Settings → Secrets and variables → Actions.
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
Loading