Repository navigation
chore: switch to the pnpm v13 lockfile format - #1137
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
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.
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.9You can send follow-ups to the cloud agent here.
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>
cf30530 to
d71c0cb
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
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.
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.
| "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" |
There was a problem hiding this comment.
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.
Reviewed by Cursor Bugbot for commit d71c0cb. Configure here.



Switches
pnpm-lock.yamlto 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: setlockfile.format: v13.package.json: bumpedpackageManagerfrompnpm@12.18.0topnpm@12.21.0, the release with the latest v13 fixes.pnpm-lock.yaml: regenerated. The project lockfile now haslockfileVersion: "13.0". Resolved package versions are unchanged.vercel.json: the install and build commands put Corepack's pnpm first onPATH, so the deploy uses thepackageManagerpnpm 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.