🐛 fix(docker): replace pnpm init with static package.json in /deps#14576
Merged
Conversation
`pnpm init` writes `devEngines.packageManager: { version: "^11.0.9" }`
into the generated package.json. corepack@latest rejects ranges in this
field with "Invalid package manager specification ... expected a semver
version", causing the subsequent `pnpm add pg drizzle-orm` to exit 1.
Skip init and write a minimal package.json directly so corepack has
nothing to validate.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
gfsaaser24
added a commit
to gfsaaser24/lobehub
that referenced
this pull request
May 22, 2026
Cherry-picks upstream lobehub#14576 (8ed31df, 2026-05-09). `pnpm init` in pnpm v11+ writes devEngines.packageManager.version as a semver range, which corepack then rejects ("Invalid package manager specification ... expected a semver version"). Coolify build server's node:22-slim image picked up a newer corepack and started failing builds. Static package.json sidesteps the pnpm/corepack incompat without pinning anything. Refs: pnpm/pnpm#11388 pnpm/pnpm#11732 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mrsimpson
pushed a commit
to mrsimpson/lobehub
that referenced
this pull request
May 29, 2026
…obehub#14576) `pnpm init` writes `devEngines.packageManager: { version: "^11.0.9" }` into the generated package.json. corepack@latest rejects ranges in this field with "Invalid package manager specification ... expected a semver version", causing the subsequent `pnpm add pg drizzle-orm` to exit 1. Skip init and write a minimal package.json directly so corepack has nothing to validate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docker PR Build (#14563 run 25597803295) was failing at the
[builder 7/11]step:Root cause:
pnpm init(pnpm 10.33) writes adevEngines.packageManager: { version: "^11.0.9" }field into the generatedpackage.json. The next command (pnpm add pg drizzle-orm) triggerscorepack@latestto validate that field — it rejects ranges and aborts.Fix: skip
pnpm initand write a minimal staticpackage.jsonso corepack has nothing to validate.Test plan
release/weekly-20260509, Docker PR Build 🚀 release: 20260509 #14563 turns green