chore(DX-809): update to use preferred OIDC for npm publish in github actions #542
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.
This PR converts the existing GitHub Action (GHA) workflow to use npmjs.com 's preferred authentication method (OIDC) to publish. "Classic tokens" that are currently configured (and dropped in this PR) will no longer work as of earlier this week.
I have manually tested this configuration works - published (then unpublished) a test version to the package managed by this repo.
Note - npmjs.com only allows a single GHA file to be configured to publish via OIDC configs, so I have dropped the manual publish step (and its script) in this repo. Please comment if this is a concern.
Note
Switches npm publish to OIDC in the deploy workflow, updating permissions and deploy steps to publish directly with npm.
/.github/workflows/deploy-sdk.yml:permissions.id-token: write.deploy-npmjob:environment: releaseand configureactions/setup-nodewithregistry-url.npm ci, runpre-deploy, andnpm publish --tag latest.NPM_TOKEN,./scripts/deploy-code.sh) in favor of direct publish.Written by Cursor Bugbot for commit 12daa5c. This will update automatically on new commits. Configure here.