Skip to content

fix(release): don't configure an npm token registry so OIDC trusted publishing can run #237

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
cipolleschi merged 1 commit into from
Jul 8, 2026
Merged

fix(release): don't configure an npm token registry so OIDC trusted publishing can run #237

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: 6 additions & 1 deletion .github/workflows/release.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,12 @@ jobs:
uses: actions/setup-node@v4.0.0
with:
node-version: 'lts/*'
registry-url: 'https://registry.npmjs.org'
# NOTE: intentionally NOT setting `registry-url` here.
# `registry-url` makes setup-node inject a job-wide NODE_AUTH_TOKEN and
# write an .npmrc with `_authToken=${NODE_AUTH_TOKEN}`. npm trusted
# publishing (OIDC) only activates when NO auth token is configured, so
# configuring a token would make `npm publish` skip OIDC entirely.
# The default registry is already https://registry.npmjs.org/.
- name: Determine new template version
run: echo "VERSION=$(./scripts/bumpedTemplateVersion.sh ${{ inputs.version }})" >> $GITHUB_ENV
- name: Update versions to input one
Expand Down
Loading