Skip to content

Update release workflow to use trusted publishing#273

Merged
franciscocardoso merged 1 commit intomasterfrom
support/oidc-release
Feb 16, 2026
Merged

Update release workflow to use trusted publishing#273
franciscocardoso merged 1 commit intomasterfrom
support/oidc-release

Conversation

@risantos
Copy link
Member

Description

Copilot AI review requested due to automatic review settings January 19, 2026 14:42
@risantos risantos requested review from a team as code owners January 19, 2026 14:42
@risantos risantos self-assigned this Jan 19, 2026
@risantos risantos added the dependencies Pull requests that update a dependency file label Jan 19, 2026
Copy link

Copilot AI left a 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 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-it from v19.0.3 to v19.2.3 with skipChecks: true configuration
  • 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: write permission 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.

@risantos risantos force-pushed the support/oidc-release branch from 838f3b1 to d1cf134 Compare February 16, 2026 10:24
@franciscocardoso franciscocardoso merged commit fa20866 into master Feb 16, 2026
3 checks passed
@franciscocardoso franciscocardoso deleted the support/oidc-release branch February 16, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments