fix: add --access public flag to GitHub Packages publish with provenance #196
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
When publishing to GitHub Packages with the --provenance flag, npm requires explicitly setting --access public. This fixes the npm publish error: "Can't generate provenance for new or private package, you must set access to public" Changes: - Added --access public flag to auto-release.yml GitHub Packages publish step - Added --access public flag to release.yml GitHub Packages publish step - Added clarifying comment about the requirement This ensures SLSA provenance generation works correctly for GitHub Packages.
Contributor
size-limit report 📦
|
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.
When publishing to GitHub Packages with the --provenance flag, npm requires explicitly setting --access public. This fixes the npm publish error: "Can't generate provenance for new or private package, you must set access to public"
Changes:
This ensures SLSA provenance generation works correctly for GitHub Packages.