chore: bump pnpm to 11.1.2#1609
Conversation
✅ Deploy Preview for viteplus-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8413589bd8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "node": ">=22.18.0" | ||
| }, | ||
| "packageManager": "pnpm@10.33.2" | ||
| "packageManager": "pnpm@11.1.2" |
There was a problem hiding this comment.
Updating only the root packageManager to pnpm@11.1.2 introduces a split with docs/package.json (still pnpm@10.33.2), so Corepack will run different pnpm majors depending on the working directory (cd docs vs repo root). This makes local docs installs and CI docs installs (pnpm -C docs ... from root) non-reproducible across environments and can lead to lockfile/behavior drift that is hard to diagnose.
Useful? React with 👍 / 👎.
fengmk2
added
test: e2e
fengmk2
force-pushed
the
chore/bump-pnpm-11.1.2
branch
from
ba13d1e to
8f2f56b
Compare
|
It looks like we need to refactor the e2e test config script. Let's wait for #1588 to be merged first before continuing to avoid a large number of conflicts. cc @Brooooooklyn |
2 participants
Bumps the repo-root
packageManagerpin topnpm@11.1.2.Only the root
package.jsonpackageManagerfield is changed.