Skip to content

ci: publish to npm via OIDC trusted publishing - #734

Merged
mccmrunal merged 1 commit into
mainfrom
ci/npm-oidc-trusted-publishing
Jul 18, 2026
Merged

ci: publish to npm via OIDC trusted publishing#734
mccmrunal merged 1 commit into
mainfrom
ci/npm-oidc-trusted-publishing

Conversation

@mccmrunal

Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI review requested due to automatic review settings July 18, 2026 05:05
@mccmrunal
mccmrunal merged commit 05d451c into main Jul 18, 2026
17 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the manual release workflow to publish to npm using OIDC trusted publishing (rather than an npm token), aligning the release pipeline with npm’s provenance/trusted publisher model.

Changes:

  • Removes NODE_AUTH_TOKEN usage so npm authentication is performed via OIDC trusted publishing.
  • Adds a step to upgrade npm to a version that supports OIDC trusted publishing.
  • Removes explicit registry-url configuration from actions/setup-node.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +45 to +47
- name: Upgrade npm for OIDC trusted publishing
# trusted publishing (OIDC) requires npm >= 11.5.1
run: npm install -g npm@latest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants