Update Rancher Shell releases to use trusted providers #16166
Merged
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.
Summary
This updates the Rancher Shell releases to use trusted providers instead of the npm token.
Occurred changes and/or fixed issues
Technical notes summary
See the trusted publishing docs on npm1. This is now the preferred approach to publishing packages.
Areas or cases that should be tested
After merge, release a new version of Rancher Shell.
Areas which could experience regressions
Publishing Rancher Shell.
Screenshot/Video
NA
Checklist
Admin,Standard UserandUser BaseFootnotes
https://docs.npmjs.com/trusted-publishers ↩