-
Notifications
You must be signed in to change notification settings - Fork 29
chore: Add trusted publisher #299
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.
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
Conversation
|
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR migrates the NPM publishing process from classic tokens to trusted publishers using OpenID Connect (OIDC) authentication, following NPM's recent revocation of classic tokens. The changes configure both the semantic-release plugin and GitHub Actions workflow to support provenance generation with OIDC.
Key changes:
- Added OIDC permissions and provenance configuration to enable trusted publishing
- Updated Node.js version from 18.x to 20 with npm@latest
- Replaced NPM_TOKEN secret with OIDC-based authentication using NPM_CONFIG_PROVENANCE
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.releaserc.json |
Configured @semantic-release/npm plugin with provenance enabled for attestation generation |
.github/workflows/release.yml |
Added OIDC permissions (id-token, contents), updated Node.js to v20, removed NPM_TOKEN in favor of NPM_CONFIG_PROVENANCE environment variable |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
### [8.2.4](8.2.3...8.2.4) (2025-12-08) ### Library - Fixes * Add edge parameter support for regional authentication ([#298](#298)) ([9f023f4](9f023f4)) * Regional Endpoint Processing ([#296](#296)) ([b3786ca](b3786ca)), closes [#297](#297) ### Library - Chores * add npm token for semantic-release authentication ([e13b03c](e13b03c)) * Add trusted publisher ([#299](#299)) ([a544aea](a544aea)) * remove registry url ([6a1c488](6a1c488))



Fixes
Following the recent revocation of NPM classic tokens, this PR migrates the release process to use trusted publishers. Documentation: https://docs.npmjs.com/trusted-publishers
Since we are releasing using semantic-release which internally handles
npm publishwe are setting provenance as true explicitly.Checklist
If you have questions, please file a support ticket, or create a GitHub Issue in this repository.