Skip to content

ci: use npm Trusted Publishers for release workflow #27

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

ci: use npm Trusted Publishers for release workflow #27

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
6 changes: 3 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,10 @@ jobs:
- run: pnpm build

- name: Create Release (if needed)
# Uses OIDC trusted publishing - no NPM_TOKEN needed
# See: https://docs.npmjs.com/trusted-publishers
env:
GH_TOKEN: ${{ github.token }}
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
NPM_CONFIG_PROVENANCE: true
run: |
# Skip release on root commit (no parent)
if ! git rev-parse HEAD^ > /dev/null 2>&1; then
Expand All @@ -60,7 +60,7 @@ jobs:
else
echo "New release needed"
gh release create "$PKG_VER" -t "$PKG_VER" --generate-notes
# publish to npm (--access public required for scoped packages with provenance)
# Publish via OIDC trusted publishing (provenance auto-generated)
pnpm publish --no-git-checks --access public
# Add the release information to the github actions summary
echo "# New Release Created" >> $GITHUB_STEP_SUMMARY
Expand Down