Skip to content

chore(deps-dev): bump eslint-config-next from 16.3.6 to 16.3.8 #25

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
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps-dev): bump eslint-config-next from 16.3.6 to 16.3.8 #25

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
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"@types/react-dom": "^19",
"@vitejs/plugin-react": "^6.0.2",
"eslint": "^9",
"eslint-config-next": "16.3.6",
"eslint-config-next": "16.3.8",

@justalab-agents justalab-agents Bot Oct 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[WARNING] agentic/design

eslint-config-next (16.3.8) is now two patch versions ahead of next (16.3.6 in dependencies). These two packages are released in lockstep by the Next.js team and are designed to match exactly — eslint-config-next re-exports @next/eslint-plugin-next at the same version, which contains lint rules that may reference APIs and patterns specific to the corresponding Next.js release. Running a mismatched pair can cause false positives (new rules flagging valid 16.3.6 patterns) or false negatives (lint rules not checking for issues that exist in 16.3.6). The standard practice is to keep both at the same version.

Suggested fix:

Either bump `next` to `16.3.8` in `dependencies` to match, or revert `eslint-config-next` back to `16.3.6` until `next` itself is ready to be upgraded:

```json
"dependencies": {
  ...
  "next": "16.3.8",
  ...
},
"devDependencies": {
  ...
  "eslint-config-next": "16.3.8",
  ...
}


<!-- justalab-agents:hash:4fe899dc1c4d -->

"jsdom": "^29.1.1",
"tailwindcss": "^4",
"typescript": "^5",
Expand Down
Loading
Loading