Skip to content

chore(deps): bump next to 16.2.6 #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
charlesrhoward wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): bump next to 16.2.6 #256

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
123 changes: 65 additions & 58 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions web/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
"fumadocs-core": "^16.7.6",
"fumadocs-mdx": "^14.2.11",
"fumadocs-ui": "^16.7.6",
"next": "^16.2.1",
"next": "^16.2.6",
"react": "^19.2.4",
"react-dom": "^19.2.4",
"three": "^0.182.0",
Expand All @@ -37,7 +37,7 @@
"@types/react-dom": "^19.1.0",
"@types/three": "^0.182.0",
"eslint": "^9.39.4",
"eslint-config-next": "^16.2.1",
"eslint-config-next": "^16.2.6",
Copy link
Copy Markdown

@mogplex mogplex Bot May 15, 2026

Choose a reason for hiding this comment

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

Warning: @next/eslint-plugin-next pinned at 16.2.1 while eslint-config-next was bumped to ^16.2.6

eslint-config-next was updated to ^16.2.6 but @next/eslint-plugin-next in devDependencies is still pinned to exactly 16.2.1. The lock file resolves both versions simultaneously — eslint-config-next@16.2.6 pulls in its own @next/eslint-plugin-next@16.2.6 transitively, while the explicitly-declared 16.2.1 copy is installed but unused. This is inconsistent: lint runs will silently use the 16.2.6 rules from the transitive dependency, but the explicit declaration signals 16.2.1 to any developer reading package.json. Update the explicit pin to 16.2.6 (or ^16.2.6) to deduplicate the lock file entry and keep tooling declarations honest.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 15, 2026

Choose a reason for hiding this comment

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

P2 Badge Bump @next/eslint-plugin-next with eslint-config-next

Updating eslint-config-next to ^16.2.6 without also updating the directly imported @next/eslint-plugin-next leaves linting on the old 16.2.1 ruleset, because web/eslint.config.mjs uses @next/eslint-plugin-next explicitly (import nextPlugin ... and spreads nextPlugin.configs.*). This introduces a version split in the same commit (16.2.1 direct plugin vs 16.2.6 config dependency), so the intended lint-rule update does not actually apply to this project.

Useful? React with 👍 / 👎.

"eslint-plugin-react": "7.37.5",
"eslint-plugin-react-hooks": "7.0.1",
"globals": "17.4.0",
Expand Down
Loading