ci: restore npm provenance for published packages - #2236
Merged
Conversation
trivikr
enabled auto-merge (squash)
August 15, 2026 17:09
kuhe
approved these changes
Aug 15, 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
2 participants
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.
Issue #, if available:
Refs: #2235
Description of changes:
Provenance attestations stopped being generated with the migration to changesets v3. Changesets v2 always shelled out to
npm publish, which attaches provenance automatically under trusted publishing. v3 selects the publish tool from the repo's package manager, so this repo now publishes viayarn npm publish, and Yarn skips provenance silently unless it is explicitly requested. The first affected release was@smithy/undici-http-handler@3.2.0.Opt in on the release step. Both variables are set so the attestationis generated whichever tool changesets selects: Yarn reads
YARN_NPM_PUBLISH_PROVENANCE, and npm/pnpm readNPM_CONFIG_PROVENANCE.Note that Yarn's own
--provenancehelp text names YARN_NPM_CONFIG_PROVENANCE, which is wrong: it resolves to an unknownnpmConfigProvenancesetting and aborts the command.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.