-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: sign npm package #21608
feat: sign npm package #21608
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you sure this works with semantic release and will not blocked by npmjs?
semantic release uses npm directly to publish1 so it should work. And this feature is in public preview, so no configuration required. I just published Footnotes |
I'm going ahead with the merge, and will closely monitor the package publish. |
🎉 This PR is included in version 35.55.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
excited to see you adopting this so quickly. i haven't even had the chance to update the docs for semantic-release for this quite yet. i can confirm that setting either in the |
The publish failed:
https://github.com/renovatebot/renovate/actions/runs/4747207723/jobs/8431810108 |
Changes
Sign Renovate packages when published
Context
https://github.blog/2023-04-19-introducing-npm-package-provenance/
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: