chore: raise the pnpm pin to ^12.4.1 - #2012
Merged
dinwwwh merged 1 commit intoSep 12, 2026
Merged
Conversation
Cloudflare Workers Builds runs pnpm through Corepack, which resolves the devEngines range to the newest 12.x on npm and does not let pnpm switch to the version recorded in pnpm-lock.yaml. With the lockfile still pinning 12.0.0, `pnpm install --frozen-lockfile` failed with ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE. The pin now matches what Corepack resolves today.
Contributor
|
This run was cancelled 🛑 The workflow was cancelled before completion. Please check the link below for details. |
This was referenced Sep 12, 2026
dinwwwh
added a commit
to middleapi/openapi-spec
that referenced
this pull request
Sep 12, 2026
Raises the pnpm pin in `devEngines.packageManager` from `^12.0.0` to `^12.4.1` and records 12.4.1 in `pnpm-lock.yaml` (previously 12.0.0), the same change as middleapi/orpc#2012. With a range pin, any environment that launches pnpm through Corepack resolves the range to the newest 12.x on npm and cannot switch to the version recorded in the lockfile, so an older lockfile pin fails `pnpm install --frozen-lockfile` with `ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE`. Keeping the pin at the current release avoids that. ## Behavior - The lockfile diff is limited to the `packageManagerDependencies` block and the `@pnpm/exe.*` platform packages for 12.4.1. - The next pnpm 12.x release needs another refresh (`pnpm self-update <version>` followed by `pnpm install`). ## Testing - `pnpm install --frozen-lockfile` passes with pnpm 12.4.1: the supply-chain check passes and the resolution step is skipped. - `eslint package.json` passes.
dinwwwh
added a commit
to middleapi/standard-server
that referenced
this pull request
Sep 12, 2026
Raises the pnpm pin in `devEngines.packageManager` from `^12.0.0` to `^12.4.1` and records 12.4.1 in `pnpm-lock.yaml` (previously 12.3.4), the same change as middleapi/orpc#2012. With a range pin, any environment that launches pnpm through Corepack resolves the range to the newest 12.x on npm and cannot switch to the version recorded in the lockfile, so an older lockfile pin fails `pnpm install --frozen-lockfile` with `ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE`. Keeping the pin at the current release avoids that. ## Behavior - The lockfile diff is limited to the `packageManagerDependencies` block and the `@pnpm/exe.*` platform packages for 12.4.1. - The next pnpm 12.x release needs another refresh (`pnpm self-update <version>` followed by `pnpm install`). ## Testing - `pnpm install --frozen-lockfile` passes with pnpm 12.4.1: the supply-chain check passes and the resolution step is skipped. - `eslint package.json` passes.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
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.
Raises the pnpm pin in
devEngines.packageManagerfrom^12.0.0to^12.4.1and records 12.4.1 inpnpm-lock.yaml. This unblocks the docs deploy: Cloudflare Workers Builds launches pnpm through Corepack, which resolves the range to the newest 12.x on npm (12.4.1 today) and does not let pnpm switch to the version recorded in the lockfile, sopnpm install --frozen-lockfilefailed withERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILEwhile the lockfile still pinned 12.0.0.Behavior
packageManagerDependenciesblock and the@pnpm/exe.*platform packages for 12.4.1.pnpm self-update <version>followed bypnpm install).Testing
pnpm install --frozen-lockfilepasses with pnpm 12.4.1 launched the way Corepack launches it (COREPACK_ROOTset,CI=true, cold policy cache): the supply-chain check passes and the resolution step is skipped.eslint package.jsonpasses.