Repository navigation
chore: @W-24716568: migrate NPM publishing to trusted publishing - #71
Merged
Merged
Conversation
k80bowman
approved these changes
Nov 9, 2026
deepti-sf
marked this pull request as ready for review
November 9, 2026 21:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: addid-token: write/contents: readpermissions andtrustedPublishing: trueon thenpmjob.dev-scriptsupgrade needed (already ^15.0.0); nonpm shrinkwrapusage.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@