Skip to content

NPM trusted publishers pipeline#8

Merged
gblikas merged 1 commit intomainfrom
cursor/npm-trusted-publishers-pipeline-0282
Jan 22, 2026
Merged

NPM trusted publishers pipeline#8
gblikas merged 1 commit intomainfrom
cursor/npm-trusted-publishers-pipeline-0282

Conversation

@gblikas
Copy link
Copy Markdown
Owner

@gblikas gblikas commented Jan 22, 2026

Upgrade publish.yml to use NPM's Trusted Publishers for more secure, token-less publishing with provenance.


Open in Cursor Open in Web


Note

Moves npm publishing to NPM Trusted Publishers (OIDC) with provenance and improves tag handling.

  • Grants id-token: write permission and publishes with --provenance
  • Drops token-based auth (NODE_AUTH_TOKEN, always-auth) in favor of OIDC
  • actions/checkout now checks out ${{ github.event.release.tag_name || inputs.tag }} to support manual dispatch
  • Retains tag presence/version verification before publish

Written by Cursor Bugbot for commit b4cb5f1. Configure here.

- Add id-token: write permission for OIDC authentication
- Remove NODE_AUTH_TOKEN secret dependency
- Add --provenance flag to enable provenance attestation
- Remove always-auth (not needed with OIDC)
- Fix checkout ref to handle workflow_dispatch inputs

NPM Trusted Publishers uses OIDC to establish trust between
GitHub Actions and npm, eliminating the need for long-lived
npm tokens stored as repository secrets.

Co-authored-by: georgeb <georgeb@bentimagelab.com>
@cursor
Copy link
Copy Markdown

cursor Bot commented Jan 22, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Jan 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
querykit Ready Ready Preview, Comment Jan 22, 2026 11:04pm

@gblikas gblikas marked this pull request as ready for review January 22, 2026 23:04
Copy link
Copy Markdown
Owner Author

@gblikas gblikas left a comment

Choose a reason for hiding this comment

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

Upgrades to NPM trusted publishing

@gblikas gblikas merged commit ee482ff into main Jan 22, 2026
6 checks passed
@gblikas gblikas deleted the cursor/npm-trusted-publishers-pipeline-0282 branch January 22, 2026 23:09
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: pnpm publish --no-git-checks --access public
- name: Publish package to npmjs with provenance
run: pnpm publish --no-git-checks --access public --provenance
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

pnpm version 8 may not support provenance

High Severity

The workflow uses pnpm publish --provenance with pnpm version 8, but pnpm may not fully support the --provenance flag in that version. This could cause the publish step to fail with an unrecognized flag error, or publish without generating provenance attestations, defeating the purpose of this upgrade. The --provenance feature is specific to npm and may require a newer pnpm version or explicit compatibility verification.

Additional Locations (1)

Fix in Cursor Fix in Web

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