Skip to content

fix: configure npm OIDC authentication for publishing#12

Merged
antomorel merged 1 commit into
mainfrom
fix/npm-oidc-auth
May 20, 2026
Merged

fix: configure npm OIDC authentication for publishing#12
antomorel merged 1 commit into
mainfrom
fix/npm-oidc-auth

Conversation

@antomorel
Copy link
Copy Markdown
Collaborator

Summary

  • Add actions/setup-node step with registry-url to enable OIDC authentication
  • Enable NPM_CONFIG_PROVENANCE for provenance attestation
  • Remove unused empty NPM_TOKEN workaround

This fixes the ENEEDAUTH error when publishing to npm by properly configuring OIDC-based authentication.

Copilot AI review requested due to automatic review settings May 20, 2026 14:03
@antomorel antomorel merged commit 7992d05 into main May 20, 2026
9 checks passed
@antomorel antomorel deleted the fix/npm-oidc-auth branch May 20, 2026 14:03
Copy link
Copy Markdown
Contributor

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 support npm “trusted publishing” (OIDC) and provenance attestations during changeset publish, addressing the ENEEDAUTH publish failure.

Changes:

  • Add an actions/setup-node@v4 step with registry-url configured for npm publishing.
  • Enable provenance attestation via NPM_CONFIG_PROVENANCE for the publish step.
  • Remove the empty NPM_TOKEN workaround from the publish step env.

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

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