CONTRIBUTING.md says pnpm 8.15.7+, but pnpm-lock.yaml v9.0 + packageManager [email protected]
Author: chirag127Created Jul 4, 2026Updated Jul 4, 2026
Problem
.github/CONTRIBUTING.md tells new contributors to install pnpm version 8.15.7 or higher, but the repo's lockfile requires pnpm 9+ and package.json pins pnpm 10.
Cite
.github/CONTRIBUTING.mdline 37: "pnpm (version 8.15.7 or higher)"package.jsonline 20:"packageManager": "[email protected]+sha512..."pnpm-lock.yamlline 1:lockfileVersion: '9.0'
Steps
npm i -g [email protected](following CONTRIBUTING)git clone https://github.com/idosal/git-mcp && cd git-mcppnpm install
Expected
Install succeeds.
Actual
pnpm 8 cannot parse lockfileVersion: 9.0. Either corepack silently upgrades to pnpm 10 (making the 8.15.7 guidance misleading), or the install fails outright with a lockfile-version error.
Environment
- Repo default branch
main@ HEAD as of 2026-07-04 package.jsonpackageManager:[email protected]pnpm-lock.yamllockfileVersion:9.0
Fix
Update CONTRIBUTING.md prerequisite to pnpm 10.x (or 9+), matching the pinned packageManager. One-line docs change.
Thanks for maintaining idosal/git-mcp!
Source: idosal/git-mcp