Skip to content

chore(publish): add publishConfig {access:public, provenance:true} across 131 npm packages#284

Closed
John-David Dalton (jdalton) wants to merge 1 commit intomainfrom
chore/publishconfig-provenance
Closed

chore(publish): add publishConfig {access:public, provenance:true} across 131 npm packages#284
John-David Dalton (jdalton) wants to merge 1 commit intomainfrom
chore/publishconfig-provenance

Conversation

@jdalton
Copy link
Copy Markdown
Collaborator

Summary

  • Bulk-add publishConfig: {access: "public", provenance: true} to every package.json under packages/npm/*.
  • Pins access + provenance attestation to each package manifest so the policy survives any direct-publish path that bypasses the workflow's --provenance CLI flag.
  • 131 packages updated; no other key-ordering changes.

Test plan

  • Next workflow-driven publish includes provenance attestation on every published package
  • CI green

…ross all 131 npm packages

Pins access + provenance attestation to each package manifest so
the policy survives any direct publish path that bypasses the
workflow's --provenance CLI flag. Bulk-applied via a one-shot
JSON-merge script; no other key ordering changes.
@jdalton
Copy link
Copy Markdown
Collaborator Author

Switching to direct push to main per repo policy.

@jdalton John-David Dalton (jdalton) deleted the chore/publishconfig-provenance branch May 1, 2026 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant