ci(publish.yml): add npm provenance statements #29
Conversation
This file contains 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
See https://docs.npmjs.com/generating-provenance-statements This increases supply-chain security for the packages, since it publicly establish where a package was built (here, in GitHub Actions) and who published a package. See https://prisma-company.slack.com/archives/C1FPU5FPT/p1698675822988359 I switched to Node.js 20, like in prisma/prisma for publishing (we need to have a more recent version of npm for provenances) Similar to prisma/engines-wrapper#476
SevInf
approved these changes
Nov 14, 2023
|
Will wee need to publish a new version now? |
|
@SevInf No urgency, but if you want to try it now, It's good to know if it actually works. (it should work ™️) |
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.
See https://docs.npmjs.com/generating-provenance-statements This increases supply-chain security for the packages, since it publicly establish where a package was built (here, in GitHub Actions) and who published a package.
See https://prisma-company.slack.com/archives/C1FPU5FPT/p1698675822988359
I switched to Node.js 20, like in prisma/prisma for publishing (we need to have a more recent version of npm for provenance statements)
Similar to prisma/engines-wrapper#476