Skip to content

chore: @W-24716568: migrate NPM publishing to trusted publishing - #71

Merged
deepti-sf merged 1 commit into
mainfrom
W-24716568-npm-trusted-publishing
Nov 9, 2026
Merged

deepti-sf merged 1 commit into
mainfrom
W-24716568-npm-trusted-publishing

Conversation

@deepti-sf

Copy link
Copy Markdown
Contributor

Migrates the release workflow to NPM Trusted Publishing (OIDC), replacing the bypass-2fa token that expires Nov 12, 2026. Follows the Platform CLI example in salesforcecli/plugin-api#228.

  • onRelease.yml: add id-token: write / contents: read permissions and trustedPublishing: true on the npm job.
  • No dev-scripts upgrade needed (already ^15.0.0); no npm shrinkwrap usage.

Do not merge yet. Trusted publishing must be configured on the NPM side by the Platform CLI team first. After merge, a release must happen within 24h of that configuration.

@W-24716568@

@deepti-sf deepti-sf changed the title chore: migrate NPM publishing to trusted publishing fix @W-24716568: migrate NPM publishing to trusted publishing Nov 9, 2026
@deepti-sf deepti-sf changed the title fix @W-24716568: migrate NPM publishing to trusted publishing chore: @W-24716568: migrate NPM publishing to trusted publishing Nov 9, 2026
@deepti-sf
deepti-sf marked this pull request as ready for review November 9, 2026 21:04
@deepti-sf
deepti-sf merged commit 84d8aa7 into main Nov 9, 2026
26 checks passed
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