[Brooooooklyn]

The v0.10.9 publish run failed before publishing because npm install -g npm@latest resolved to npm 12, whose engine now requires Node ^22.22.2 || ^24.15.0 || >=26.0.0; the release workflow currently uses Node 24.13.1 from .node-version.

This pins the release workflow to npm 11, whose current npm metadata supports Node ^20.17.0 || >=22.9.0, so it remains compatible with the workflow runtime.

Verification:

• npm view npm@11 version engines --json
• vp check

---

Note

Low Risk
CI-only change to the global npm version on publish; no application or package runtime behavior changes.

Overview
The Publish workflow no longer runs npm install -g npm@latest before vp pm publish. It installs npm@11 instead so the global npm used at release time stays on a major line whose Node engine range still matches Node 24.13.1 from .node-version.

This avoids publish jobs failing when npm@latest resolves to npm 12, which requires newer Node versions than the workflow currently uses.

^{Reviewed by Cursor Bugbot for commit 43ef203. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_51be2b85-c7f3-4e1d-a131-43a50a08ab4d)