chore: raise the pnpm pin to ^12.4.1 - #14
Merged
Merged
Conversation
Keeps the devEngines range and the pnpm-lock.yaml pin at the current pnpm 12.x release. Environments that launch pnpm through Corepack resolve the range to the newest 12.x and cannot switch to the lockfile's version, so an older lockfile pin fails frozen installs.
|
This run was cancelled 🛑 The workflow was cancelled before completion. Please check the link below for details. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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(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 failspnpm install --frozen-lockfilewithERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE. Keeping the pin at the current release avoids that.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: the supply-chain check passes and the resolution step is skipped.eslint package.jsonpasses.