update to support npm provenance attestation #225
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.
Pull Request
Description
This PR updates packages and the publish pipeline to support NPM's package signing capabilities.
This may not work due to beachball not supporting the
--provenance
flag yet, however npm provides alternative methods for enabling the feature here that I ended up using.This is necessary to build and maintain trust with users as supply chain attacks become more prevalent in the ecosystem. We already use scoped packages which mitigates the risk, this just adds an extra layer.
Issues
Reviewer Notes
Test Plan
After the next release, check each publish package on npm to see if the provenance statement has been generated.
Checklist
General
Component-specific
⏭ Next Steps