Skip to content

Re-enable npm provenance (merge after repo is public) #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nrodd wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Re-enable npm provenance (merge after repo is public) #12

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ jobs:
run: npm run build

- name: Publish npm package
# NO --provenance: npm rejects provenance attestations from private
# source repos (E422 "Unsupported ... visibility: private"). This repo
# is private, so provenance was intentionally dropped in 059d114.
run: npm publish --access public
# --provenance is automatic under trusted publishing, but explicit is
# self-documenting. Only valid once the source repo is PUBLIC — npm
# rejects provenance from private repos (E422).
run: npm publish --access public --provenance
3 changes: 2 additions & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,8 @@
"url": "https://github.com/fullstorydev/subtext-wizard.git"
},
"publishConfig": {
"access": "public"
"access": "public",
"provenance": true

@cursor cursor Bot Jul 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provenance blocks local npm publish

Medium Severity

Setting publishConfig.provenance to true makes every npm publish attempt Sigstore provenance, which needs a CI OIDC provider. Local publishes (including with the existing prepublishOnly script) fail with automatic provenance errors even after the GitHub repo is public. CI can use --provenance alone.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit b3c64e9. Configure here.

},
"keywords": [
"subtext",
Expand Down