e6983b911b
## Why? Notable change of v9 is Corepack is enabled by default. So we can ensure all package manage/resolved exact same version of pnpm. - [**v9.0.0**](https://github.com/pnpm/pnpm/releases/tag/v9.0.0): Discontinued support for Node.js v16 and introduced Corepack compatibility checks. New configuration updates include enabling `dedupe-injected-deps` and changing the lockfile to version 9, with better readability and resistance to Git conflicts. ... - [**v9.4.0**](https://github.com/pnpm/pnpm/releases/tag/v9.4.0) - Kudos to @ryota-murakami for the original :pr:! → https://github.com/vercel/next.js/pull/64854 ## Changes - https://pnpm.io/npmrc#link-workspace-packages defaults to `false` now, so setting it to `true` Closes NEXT-3211 |
||
|---|---|---|
| .. | ||
| actions | ||
| comments | ||
| DISCUSSION_TEMPLATE | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| labeler.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| pull_request_template.md | ||