-
Notifications
You must be signed in to change notification settings - Fork 4
DX-809 update to use preferred OIDC for npm publish in github actions #99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| uses: JS-DevTools/npm-publish@9ff4ebfbe48473265867fb9608c047e7995edfa3 # v3.1.1 | ||
| with: | ||
| token: ${{ secrets.NPM_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using standard npm publish to and dropping the no-longer-supported auth tokens - use the OIDC config, instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any concerns on using the standard npm publish over this custom publish action ?
Note
Migrates the release workflow to OIDC-based npm publish, adds required permissions, and updates GitHub Actions to v4.
.github/workflows/release.yml:permissions(id-token: write,contents: read), sets registry URL, installs latest npm, and replacesJS-DevTools/npm-publishwithnpm publish.actions/checkouttov4andactions/setup-nodetov4; uses Node.js20.environment: release.Written by Cursor Bugbot for commit e10ad9c. This will update automatically on new commits. Configure here.