Skip to content

chore: fix deploy by hardcoding npm 11 #103

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

Merged
metalwarrior665 merged 3 commits into from
Jul 10, 2026
+3 −1
Merged

chore: fix deploy by hardcoding npm 11 #103

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5fb501e
fix: handle npm 12 versions --json output in beta release script
claude Jul 10, 2026
e5e8b1e
fix: pin npm to v11 in publish workflow to avoid broken provenance
claude Jul 10, 2026
d7d0deb
Merge branch 'master' into claude/npm-publish-failure-fakyxq
metalwarrior665 Jul 10, 2026
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
4 changes: 3 additions & 1 deletion .github/workflows/manual_publish_to_npm.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,9 @@ jobs:
cache: 'npm'
cache-dependency-path: 'package-lock.json'
- name: Update npm
run: npm install -g npm@latest
# Pin to npm 11: npm 12.0.0 ships a broken `libnpmpublish` that requires the
# top-level `sigstore` module without bundling it, breaking `npm publish --provenance`.
run: npm install -g npm@11
- name: Install dependencies
run: npm ci
- name: Bump pre-release version
Expand Down
Loading