Skip to content

ci: release pipeline #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
MarioCadenas merged 1 commit into from
Dec 27, 2025
Merged

ci: release pipeline #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
13 changes: 8 additions & 5 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,16 @@ jobs:
pull-requests: write # to be able to comment on released pull requests
id-token: write # to enable use of OIDC for npm provenance
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4

- name: Setup Node.js 22.x
uses: actions/setup-node@v3
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: 22.x
node-version: '22.14'
registry-url: 'https://registry.npmjs.org'

- name: Upgrade npm for OIDC support
run: npm install -g npm@latest

- name: Install dependencies
run: npm ci
Expand All @@ -33,5 +37,4 @@ jobs:
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
HUSKY: 0
NPM_CONFIG_PROVENANCE: true
Copy link
Copy Markdown

@cursor cursor bot Dec 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing NODE_AUTH_TOKEN for npm authentication

The registry-url configuration in actions/setup-node creates an .npmrc file that expects NODE_AUTH_TOKEN for authentication. However, the "Publish to npm" step's environment only includes GITHUB_TOKEN and HUSKY - no NODE_AUTH_TOKEN is provided. This will likely cause npm publishing to fail with authentication errors since the generated .npmrc references an undefined token variable.

Additional Locations (1)

Fix in Cursor Fix in Web

run: npx semantic-release
Loading