Repository navigation
fix(publish): honor provenance in PNPM 11+ - #141
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the publish-if-not-exists composite action so provenance publishing continues to work when callers use pnpm 11+, which no longer reads NPM_CONFIG_PROVENANCE.
Changes:
- Adds a new optional
provenanceinput to explicitly control provenance (true/false/ empty to defer). - Introduces a “Resolve provenance” step that normalizes provenance preference across
inputs.provenance,NPM_CONFIG_PROVENANCE, andPNPM_CONFIG_PROVENANCE, and exports both env vars for the publish step.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
sea-grass
approved these changes
Aug 27, 2026
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
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.
Pnpm 11+ no longer honors
NPM_CONFIG_PROVENANCE, so repos upgrading to pnpm 11 would no longer be able to publish.contributes to KKN-927