ci: configure release workflow to use trusted publishing #423
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.
Description
This PR configures the release workflow to use trusted publishing. It is needed because NPM classic tokens (presumably used in this repository currently) are going to be deprecated in November.
Before this PR can be merged, package maintainer should configure trusted publishing on npmjs.org.
After this PR is merged, we can delete the NPM_TOKEN secret from the repository secrets.
How to configure trusted publishing on npmjs.org?
filecoin-projectfilsnaprelease.ymlLink to issue
Please add a link to any relevant issues/tickets
Type of change
Please delete options that are not relevant.