Skip to content

chore: switch to the pnpm v13 lockfile format - #1137

Merged
stipsan merged 1 commit into
mainfrom
cody/pnpm-v13-lockfile-0dd3
Nov 16, 2026
Merged

stipsan merged 1 commit into
mainfrom
cody/pnpm-v13-lockfile-0dd3

Conversation

@stipsan

@stipsan stipsan commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Switches pnpm-lock.yaml to the new v13 lockfile format, which is much less prone to Git merge conflicts. It has one entry per package version, so dependency updates touch fewer lines.

What changed:

  • pnpm-workspace.yaml: set lockfile.format: v13.
  • package.json: bumped packageManager from pnpm@12.18.0 to pnpm@12.21.0, the release with the latest v13 fixes.
  • pnpm-lock.yaml: regenerated. The project lockfile now has lockfileVersion: "13.0". Resolved package versions are unchanged.
  • vercel.json: the install and build commands put Corepack's pnpm first on PATH, so the deploy uses the packageManager pnpm 12.21.0 instead of the pnpm version Vercel picks from the lockfile. Vercel only accepts lockfile version 9 for its own pnpm 10 to 12. This works only while the project does not have Corepack mode (ENABLE_EXPERIMENTAL_COREPACK) turned on.

Note: pnpm marks the v13 format as experimental until pnpm 13.

Open in Web Open in Cursor 

@vercel

vercel Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
scroll-into-view-dev Ready Ready Preview Nov 16, 2026 4:22pm UTC

Request Review

@socket-security

socket-security Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedpostcss@​8.5.331001008295100
Addedscroll-into-view-if-needed@​3.2.11001009987100
Addedastro@​7.4.12971008898100
Addedsmooth-scroll-into-view-if-needed@​2.1.210010010089100
Addedcompute-scroll-into-view@​3.2.210010010090100

View full report

@cursor cursor Bot 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.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Autofix Details

Bugbot Autofix prepared a fix for the issue found in the latest run.

  • ✅ Fixed: Vercel may fail v13 installs
    • Removed lockfile.format: v13 and regenerated pnpm-lock.yaml as v9 so Vercel can install with pnpm 12.

Create PR

Or push these changes by commenting:

@cursor push 07d6fb1112
Preview (07d6fb1112)
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml

diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -1,5 +1,3 @@
-lockfile:
-  format: v13
 minimumReleaseAgeExclude:
   - '@astrojs/vite-plugin-astro@0.1.0'
   - astro@7.4.9

@@ -1,5 +1,3 @@
-lockfile:
-  format: v13
 minimumReleaseAgeExclude:
   - '@astrojs/vite-plugin-astro@0.1.0'
   - astro@7.4.9

You can send follow-ups to the cloud agent here.

Comment thread pnpm-workspace.yaml Resolved
Set lockfile.format to v13 in pnpm-workspace.yaml and bump pnpm to
12.21.0. The v13 format records one entry per package version, so
lockfile updates touch fewer lines and cause fewer merge conflicts.

Point Vercel's install and build commands at Corepack's pnpm so the
deploy uses pnpm 12.21.0, which can read the v13 lockfile.

Co-authored-by: Cody Olsen <stipsan@users.noreply.github.com>

@cursor cursor Bot 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.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix prepared a fix for the issue found in the latest run.

  • ✅ Fixed: Corepack missing on Node 26
    • Prepended npm install -g corepack to the Vercel install and build commands so Corepack is available on Node 26, which no longer ships it.

Create PR

Or push these changes by commenting:

@cursor push 348a726331
Preview (348a726331)
diff --git a/vercel.json b/vercel.json
--- a/vercel.json
+++ b/vercel.json
@@ -1,6 +1,6 @@
 {
   "$schema": "https://openapi.vercel.sh/vercel.json",
   "framework": "astro",
-  "installCommand": "mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm install --frozen-lockfile",
-  "buildCommand": "mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm build"
+  "installCommand": "npm install -g corepack && mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm install --frozen-lockfile",
+  "buildCommand": "npm install -g corepack && mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm build"
 }

@@ -1,6 +1,6 @@
 {
   "$schema": "https://openapi.vercel.sh/vercel.json",
   "framework": "astro",
-  "installCommand": "mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm install --frozen-lockfile",
-  "buildCommand": "mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm build"
+  "installCommand": "npm install -g corepack && mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm install --frozen-lockfile",
+  "buildCommand": "npm install -g corepack && mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm build"
 }

You can send follow-ups to the cloud agent here.

Reviewed by Cursor Bugbot for commit d71c0cb. Configure here.

Comment thread vercel.json
"framework": "astro"
"framework": "astro",
"installCommand": "mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm install --frozen-lockfile",
"buildCommand": "mkdir -p /tmp/pnpm-bin && corepack enable pnpm --install-directory /tmp/pnpm-bin && PATH=/tmp/pnpm-bin:$PATH pnpm build"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Corepack missing on Node 26

High Severity

The new installCommand and buildCommand invoke corepack, which Node.js stopped shipping in v25. This project requires Node >=26, so Vercel runs those commands on a runtime with no corepack binary and the && chain never reaches pnpm install or pnpm build.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit d71c0cb. Configure here.

@stipsan
stipsan merged commit 3ba6f6a into main Nov 16, 2026
7 checks passed
@stipsan
stipsan deleted the cody/pnpm-v13-lockfile-0dd3 branch November 16, 2026 18:01

This branch was successfully deployed

1 active deployment
Preview — d71c0cbe Deployed Nov 16, 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