Skip to content

fix(vercel): pin supported pnpm for docs deployment - #800

Merged
vastsa merged 2 commits into
mainfrom
fix/vercel-pnpm-install
Sep 21, 2026
Merged

vastsa merged 2 commits into
mainfrom
fix/vercel-pnpm-install

Conversation

@vastsa

@vastsa vastsa commented Sep 21, 2026

Copy link
Copy Markdown
Owner

Summary

  • pin the repository package manager to pnpm 10.34.5, which is supported by Vercel
  • regenerate the pnpm lockfile with the compatible patchedDependencies format
  • make Vercel use the exact pnpm version for install and VitePress build

Validation

  • npx --yes pnpm@10.34.5 install --frozen-lockfile
  • npx --yes pnpm@10.34.5 build
  • pnpm check:pr-base

The Vercel failure happened during pnpm metadata fetching before VitePress ran; vitepress was only the first package request that exposed the old/incompatible pnpm runtime.

Vercel may run an older pnpm when the install command is not pinned, which fails while fetching workspace metadata under the current Node build image. Use pnpm 10.34.5 for both installation and the VitePress build, and keep the lockfile format compatible with that version.
Copilot AI lite review requested due to automatic review settings September 21, 2026 11:27

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

The Vercel project builds from docs/, where the repository lockfile is outside the configured root directory. Keep the pnpm version pinned but let the docs-root install resolve its local manifest without requiring an unavailable lockfile.
@vastsa
vastsa merged commit 43a3737 into main Sep 21, 2026
5 checks passed
@vastsa
vastsa deleted the fix/vercel-pnpm-install branch September 24, 2026 01:54

This branch was successfully deployed

1 active deployment
Preview — 03b56a99 Deployed Sep 21, 2026 by vercel[bot]
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.

2 participants