Update release workflow to use trusted publishing#273
Merged
franciscocardoso merged 1 commit intomasterfrom Feb 16, 2026
Merged
Update release workflow to use trusted publishing#273franciscocardoso merged 1 commit intomasterfrom
release workflow to use trusted publishing#273franciscocardoso merged 1 commit intomasterfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the release workflow to use OIDC-based trusted publishing for npm, replacing traditional token-based authentication. It also upgrades the release-it tool and several GitHub Actions to newer versions.
Changes:
- Adds OIDC permissions (
id-token: write) and removes manual npm token configuration - Updates
release-itfrom v19.0.3 to v19.2.3 withskipChecks: trueconfiguration - Upgrades GitHub Actions and Node.js versions used in the release workflow
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.github/workflows/release.yaml |
Adds OIDC permissions, removes npm token configuration, updates action versions to v6, and changes Node.js version to 24 |
.release-it.js |
Adds skipChecks: true to npm configuration for trusted publishing |
package.json |
Updates release-it dependency version and reorders dependency list alphabetically |
yarn.lock |
Updates lockfile with new dependency versions for release-it and its transitive dependencies |
Comments suppressed due to low confidence (1)
.github/workflows/release.yaml:50
- The removal of npm authentication configuration suggests a transition to OIDC trusted publishing, which relies on the
id-token: writepermission instead of npm tokens. However, the PR description or code comments do not explain how the npm registry needs to be configured on the npm side to accept OIDC tokens from this GitHub Actions workflow. Ensure that the npm package has trusted publishing configured for this GitHub repository before merging.
- name: Generate release
env:
GITHUB_TOKEN: ${{ secrets.RELEASE_GITHUB_TOKEN }}
run: npm run release -- --increment "${{ github.event.inputs.VERSION_BUMP }}" -V
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
838f3b1 to
d1cf134
Compare
franciscocardoso
approved these changes
Feb 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
releaseworkflow to use OIDC publishing viarelease-it. See https://github.com/release-it/release-it/blob/3378faf75f1a8e2e87f63a4914f8df68223b3a5b/docs/npm.md#trusted-publishing-oidc