Skip to content

chore: fix deploy by hardcoding npm 11 - #103

Merged
metalwarrior665 merged 3 commits into
masterfrom
claude/npm-publish-failure-fakyxq
Jul 10, 2026
Merged

chore: fix deploy by hardcoding npm 11#103
metalwarrior665 merged 3 commits into
masterfrom
claude/npm-publish-failure-fakyxq

Conversation

@metalwarrior665

Copy link
Copy Markdown
Member

No description provided.

claude added 2 commits July 10, 2026 10:52
npm 12 changed `npm show <pkg> versions --json` to wrap the version
array in an outer array ([[...]]), which broke before-beta-release.js
with "TypeError: v.startsWith is not a function". Since the publish
workflow force-installs npm@latest, this silently regressed once npm 12
was released.

Normalize the parsed output by flattening and keeping only strings,
which also covers the case where npm returns a bare string for a
single-version package.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S3skLbP3YnDAYp124zzaS5
npm 12.0.0's bundled libnpmpublish requires the top-level `sigstore`
module but no longer bundles it, so `npm publish --provenance` fails
with "Cannot find module 'sigstore'". Pin the global npm install to
v11, which bundles sigstore and publishes correctly.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S3skLbP3YnDAYp124zzaS5
@metalwarrior665 metalwarrior665 changed the title Claude/npm publish failure fakyxq chore: fix deploy by harding npm 11 Jul 10, 2026
@metalwarrior665 metalwarrior665 changed the title chore: fix deploy by harding npm 11 chore: fix deploy by hardcoding npm 11 Jul 10, 2026
@metalwarrior665
metalwarrior665 merged commit 8c2155d into master Jul 10, 2026
10 checks passed
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.

3 participants