Enable Trusted Publishing #85
Merged
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
🦋 Changeset detectedLatest commit: cd76164 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Summary:
npmjs.com is disabling access tokens that have no expiry. As part of this, all newly generated tokens will have a limited lifetime. Instead of dealing with needing to rotate tokens across all our repos, I'm enabling Trusted Publishing (announcement) which doesn't need any tokens!
I've included a
patchchangeset in this PR so that I can cut a release to test.Issue: "none"
Test plan:
Land this PR
Cut a release
Watch the Github Action and ensure it publishes (since there's no NPM_TOKEN set up in teh publish action, it shoudl work only if Trusted Publishing is configured correctly).