ci: Update release workflow for npm OIDC authentication #60
Conversation
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
rmi22186
requested review from
alexs-mparticle,
jaissica12,
jamesnrokt and
mattbodle
rmi22186
force-pushed
the
ci/SDKE-677-add-npm-oidc-release
branch
from
47e3467 to
4bb2d22
Compare
jaissica12
force-pushed
the
ci/SDKE-677-add-npm-oidc-release
branch
from
4bb2d22 to
18bb832
Compare
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.
Instructions
developmentSummary
npm now supports OIDC and requires an update to the release.yml to support this. I already updated the Trusted Publisher information on the npm package page:
Testing Plan
Cannot test locally - it's related to releasing and will be tested in the next release workflow.
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)