Skip to content

Publish with provenance#334

Merged
dgreif merged 1 commit intomainfrom
dg/publish-provenance
Feb 9, 2026
Merged

Publish with provenance#334
dgreif merged 1 commit intomainfrom
dg/publish-provenance

Conversation

@dgreif
Copy link
Contributor

@dgreif dgreif commented Feb 8, 2026

I'd like to cut a new release, but npm has changed security quite a bit since we last published this package:

  • Adding --provenance, which gives us a nice badge in npm and points back to the workflow which built the published assets
  • Adding id-token: write, which is need for provenance, but also gives us the ability to publish without an access token since I've configured this package to publish from this repo/workflow
image

@dgreif dgreif requested a review from a team as a code owner February 8, 2026 15:36
Copilot AI review requested due to automatic review settings February 8, 2026 15:36
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

Updates the npm release workflow to use npm’s provenance feature and GitHub OIDC, enabling trusted publishing from this workflow without an npm access token.

Changes:

  • Add GitHub Actions workflow permissions required for OIDC (id-token: write) and restrict repository access (contents: read).
  • Replace token-based npm publish with npm publish --provenance.

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

@dgreif dgreif merged commit ceddf6e into main Feb 9, 2026
12 checks passed
@dgreif dgreif deleted the dg/publish-provenance branch February 9, 2026 13:59
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