chore: add provenance to release.yml #227
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.
Add npm provenance support to release workflow
https://docs.npmjs.com/generating-provenance-statements#using-third-party-package-publishing-tools
reference: lerna/lerna#3657 (comment)
What problem is this PR solving?
This PR adds npm provenance support to our release workflow. Provenance is a security feature that allows consumers of our packages to verify where they were built and published from, enhancing supply chain security. With this change, our published packages will include provenance attestations that link them back to our GitHub repository and CI process.
Reviewers' hat-rack 🎩
Before requesting reviews
Before you deploy