Skip to content

Commit b55f4f7

Browse files
committed
fix: scope OIDC automatic provenance to the current publish
The auto-enable path wrote the derived decision to the shared config at user scope. During npm publish --workspaces the config is reused across packages, so later workspaces inherited provenance: true; a later workspace with publishConfig["provenance-file"] then received both provenance and provenanceFile, tripping the new conflict check with EUSAGE and making publish success depend on workspace order. opts.provenance = true is sufficient on its own because the same opts object is passed through otplease to libnpmpublish. Explicit user configuration such as --provenance is unaffected. Refs: #9882 (comment) Signed-off-by: Yunseo Kim <[email protected]>
1 parent 6907480 commit b55f4f7

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

‎lib/utils/oidc.js‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,6 @@ async function oidc ({ packageName, registry, opts, config }) {
159159
if (visibility?.public) {
160160
log.verbose('oidc', `Enabling provenance`)
161161
opts.provenance = true
162-
config.set('provenance', true, 'user')
163162
}
164163
}
165164
}

0 commit comments

Comments
 (0)