Generate provenance statements when publishing #7
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
grzegorzkrukowski
force-pushed
the
master
branch
2 times, most recently
from
aaabb71 to
12234f8
Compare
grzegorzkrukowski
force-pushed
the
master
branch
2 times, most recently
from
9c8e587 to
1f62dfe
Compare
grzegorzkrukowski
force-pushed
the
master
branch
6 times, most recently
from
a425fd5 to
d94462b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documentation: https://docs.npmjs.com/generating-provenance-statements
It looks like your
publish-npmin-use actions are private. You need to add a new permission field to those actions to apply the provenance change: