ci: generate provenance statement on release to increase security #10773
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.
Background
Following recent hacks on npm packages, it would be greatly appreciated if you could increase the trust level of the npm packages.
Summary
I added generation of provenance statements as outlined in this guide from npm: docs.npmjs.com/generating-provenance-statements
Manual Verification
I followed the steps in the npm guide and already contributed this to other npm packages.
Checklist
pnpm changesetin the project root)Future Work
Migrating to trusted publishing could further increase security.