chore(deps): upgrade all dependencies to latest major versions#133
Conversation
- @radix-ui/react-accordion: ^1.2.12 → ^1.2.13 - next: ^16.2.6 → ^16.2.7 - @next/mdx: ^16.2.6 → ^16.2.7 - react: ^19.2.6 → ^19.2.7 - react-dom: ^19.2.6 → ^19.2.7 - @biomejs/biome: ^2.4.15 → ^2.4.16 - @types/mdx: ^2.0.13 → ^2.0.14 - @types/node: ^25.8.0 → ^25.9.2 - @types/react: ^19.2.14 → ^19.2.17 - lint-staged: ^17.0.5 → ^17.0.7 - shiki: ^4.0.2 → ^4.2.0 - ultracite: ^7.7.0 → ^7.8.2 - pnpm: 10.34.1 → 11.5.2 - Migrate pnpm.overrides from package.json to pnpm-workspace.yaml (pnpm v11 compat)
People can be co-author:
|
❌ Deploy Preview for semantic-template failed. Why did it fail? →
|
There was a problem hiding this comment.
Code Review
This pull request updates several dependencies and devDependencies in package.json, upgrades the package manager to pnpm v11.5.2, and introduces a pnpm-workspace.yaml configuration file. Feedback on the changes identifies an issue in pnpm-workspace.yaml where the deprecated or incorrect allowBuilds field is used instead of onlyBuiltDependencies to enable builds for the sharp package, which could lead to build or runtime failures in Next.js.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| allowBuilds: | ||
| sharp: true |
There was a problem hiding this comment.
In pnpm v10 and v11, the configuration to allow builds for specific dependencies is onlyBuiltDependencies (which accepts an array of package names), rather than allowBuilds with boolean values. Using allowBuilds will be ignored by pnpm, which will prevent sharp from building and potentially cause runtime or build issues in Next.js.
onlyBuiltDependencies:
- sharp
Dependency Upgrades
Dependencies
Dev Dependencies
Tooling
Additional Changes
pnpm.overridesfrompackage.jsontopnpm-workspace.yaml(required by pnpm v11)pnpm-workspace.yamlwithallowBuildsandoverridesconfigVerification
pnpm installsucceedspnpm buildsucceeds (Next.js 16.2.7, Turbopack)Closes #116 (supersedes the renovate pnpm v11 upgrade PR)