docs: Update README.md with npm package provenance#2789
Merged
travi merged 1 commit intosemantic-release:masterfrom May 9, 2023
Merged
docs: Update README.md with npm package provenance#2789travi merged 1 commit intosemantic-release:masterfrom
travi merged 1 commit intosemantic-release:masterfrom
Conversation
travi
approved these changes
May 9, 2023
Member
|
i'm merging despite that cancelled matrix verification since that is related to some known test flakiness that i havent had time to investigate yet |
Contributor
Author
|
Thanks Matt! |
|
🎉 This PR is included in version 21.0.3-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 21.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
npm package provenance is a big thing for open-source supply chain security and should receive increased awareness and promotion to help secure the ecosystem of 3rd-party packages.
Why
The npm package provenance setup exists in the semantic-release/npm package readme but it's easily missed out on when someone searches the main project's README.
The change
This PR updates the list of supported features to make the feature easily accessible and promote it for users.