Repository navigation
deps: align eslint-config-next with next 16.4.2 - #18143
Merged
Merged
Conversation
The security bump to next 16.4.2 (#18067) left eslint-config-next and its @next/eslint-plugin-next on 16.3.8. Pin them to the same release.
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The security bump to
next16.4.2 (#18067) lefteslint-config-nextand its@next/eslint-plugin-nexton16.3.8. This pins both to16.4.2, the same release asnext, so the lint rules match the framework version.eslint-config-next16.4.2 is also part of the 26-package development group #17197; this PR moves only the Next.js pair so it does not wait on that group.How
package.jsonpin changed (exact, no range, likenext), thennpm install --package-lock-only --ignore-scripts. The lockfile diff touches onlynode_modules/eslint-config-nextandnode_modules/@next/eslint-plugin-next.Validation
npm run check:lockfileeslint-config-nextand@next/eslint-plugin-next16.3.8 → 16.4.2The local
node_modulesis shared with the main checkout and was not reinstalled, so ESLint runs against 16.4.2 in CI (npm ci), not locally.