Skip to content

ci: let the first npm release publish with an NPM_TOKEN secret #3

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
iyashjayesh merged 1 commit into from
Oct 17, 2026
Merged

ci: let the first npm release publish with an NPM_TOKEN secret #3

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
15 changes: 14 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ on:
push:
tags: ["v*"]

env:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

permissions:
contents: read
id-token: write # OIDC token for npm Trusted Publishing
Expand Down Expand Up @@ -36,4 +39,14 @@ jobs:
- run: pnpm build
# Trusted Publishing needs npm 11.5.1 or later; Node 22 ships npm 10.
- run: npm install -g npm@11.5.1
- run: npm publish --access public
# Bootstrap: npm only lets a trusted publisher be attached to a package that already
# exists, so the first release can use an NPM_TOKEN secret (a granular token for the
# @flamai scope). Delete the secret once the trusted publisher is set up.
- name: Publish with NPM_TOKEN
if: env.NPM_TOKEN != ''
run: npm publish --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
- name: Publish with Trusted Publishing
if: env.NPM_TOKEN == ''
run: npm publish --access public
Loading