Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/next-app-router/next-app-router-4001/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@
"date-fns": "3.6.0",
"dinero.js": "2.0.1",
"ms": "3.0.0-canary.1",
"next": "16.1.5",
"next": "16.2.3",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regenerate lockfile after bumping Next.js

This dependency change updates apps/next-app-router/next-app-router-4001/package.json to next@16.2.3 but leaves the workspace lockfile importer entry at 16.1.5 (pnpm-lock.yaml for this app still shows next specifier/version 16.1.5). In the workflows I checked, installs run with pnpm install --frozen-lockfile (for example .github/workflows/build-and-test.yml), so this mismatch will cause install to fail before tests/builds run until pnpm-lock.yaml is regenerated and committed.

Useful? React with 👍 / 👎.

"react": "19.0.0-rc-cd22717c-20241013",
"react-dom": "19.0.0-rc-cd22717c-20241013",
"server-only": "0.0.1",
Expand Down
Loading