Skip to content
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

Enable Publish Attestation (Provenance) #1299

Merged
merged 2 commits into from
Sep 18, 2024
Merged

Conversation

elliot-huffman
Copy link
Contributor

Enable provenance on the NPM publish command so that attestation data is available in the NPM public registry to reduce the risk of a supply chain attack.

This is a non-breaking change and provides additional metadata for system that know how to consume this additional package metadata. Non-supported systems ignore this.

NPM Publish Command Docs (on provenance):
https://docs.npmjs.com/generating-provenance-statements

Semantic Release support statement:
https://github.com/semantic-release/npm?tab=readme-ov-file#npm-provenance

Enable provenance on the NPM publish command so that attestation data is available in the NPM public registry to reduce the risk of a supply chain attack.
@brettz9
Copy link
Collaborator

brettz9 commented Aug 9, 2024

@gajus : Do you want to take a look?

@gajus
Copy link
Owner

gajus commented Aug 19, 2024

This looks well intended. Not familiar with the configuration, but support it.

@brettz9 brettz9 merged commit 239d69a into gajus:main Sep 18, 2024
5 checks passed
Copy link

🎉 This issue has been resolved in version 50.2.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants