chore: update to node.js 24, pnpm 10#13423
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@wrslatz is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
The base v4 branch advanced (uuid v14 bump in the mikro-orm, neo4j, and upstash-redis adapters, plus origin-detection security fixes). Its pnpm-7 lockfile (lockfileVersion 5.4) conflicted with this PR's pnpm-10 lockfile (lockfileVersion 9.0). Resolved by keeping the pnpm-10 lockfile and regenerating it with pnpm@10.33.2 so the v4 dependency changes are incorporated. Verified with `pnpm install --frozen-lockfile`, which confirms the lockfile is consistent with every workspace package.json.
Migrating to pnpm 10 regenerates pnpm-lock.yaml, which re-resolves floating
transitive ranges to their latest versions. Two of those bumps break the v4
docs build (Docusaurus 2.1.0):
- webpack 5.95.0 -> 5.106.2: stricter ProgressPlugin schema validation
crashes the build ("options has an unknown property 'name'/'color'").
- cytoscape 3.30.2 -> 3.33.2 (via mermaid 9.4.3): its updated exports field
no longer exposes ./dist/cytoscape.umd.js, breaking the client bundle.
Pin both to the versions the v4 base branch ships via pnpm overrides so the
Docusaurus build keeps compiling. Verified locally with pnpm 10: docs build
completes successfully (client + server compiled, static files generated).
☕️ Reasoning
Update the v4 branch to use the latest supported versions of Node.js and pnpm.
🧢 Checklist
🎫 Affected issues
Closes #13421
📌 Resources