chore: generate provenance statements on release #14119
Open
+3
−0
Conversation
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
|
timdorr
approved these changes
Aug 5, 2025
brophdawg11
reviewed
Aug 6, 2025
MichaelDeBoey
force-pushed
the
generate-provenance-statements-on-release
branch
from
64ae145 to
d6f084b
Compare
brophdawg11
reviewed
Aug 6, 2025
|
I'm going to wait to merge this for an upcoming small release - maybe a quick patch following the 7.8.0 going out tomorrow. Don't want to run into anything unexpected and have to go down a rabbit hole debugging :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This will also add a new Provenance section + a verified badge next to the version (in the sidebar + versions tab) to the NPM page
More info can be found at https://docs.npmjs.com/generating-provenance-statements