chore(deps): update dependency @next/eslint-plugin-next to v16#2772
chore(deps): update dependency @next/eslint-plugin-next to v16#2772renovate[bot] wants to merge 1 commit intomainfrom
Conversation
7557cd1 to
f62137d
Compare
4c980bd to
d8a2959
Compare
1858b47 to
34d9c1e
Compare
62ac883 to
50eeb99
Compare
5a4c6e2 to
6855951
Compare
OpenAPI ChangesShow/hide No detectable change.Unexpected changes? Ensure your branch is up-to-date with |
| "version": "0.0.0", | ||
| "devDependencies": { | ||
| "@next/eslint-plugin-next": "^14.2.7", | ||
| "@next/eslint-plugin-next": "^16.0.0", |
There was a problem hiding this comment.
Bug: The upgrade to @next/eslint-plugin-next v16 requires a new "flat config" format, but the project still uses the legacy .eslintrc.js, which will cause the CI linting step to fail.
Severity: CRITICAL
Suggested Fix
Migrate the ESLint configuration from the legacy .eslintrc.js file to the new flat config format by creating an eslint.config.js or eslint.config.mjs file. This will align the project with the requirements of @next/eslint-plugin-next v16 and ensure the linting process runs correctly.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: frontends/package.json#L38
Potential issue: The project upgrades `@next/eslint-plugin-next` to v16, which is
designed for ESLint's new "flat config" format (`eslint.config.js`). However, the
repository's configuration remains in the legacy `.eslintrc.js` format. This
incompatibility will cause the `yarn lint-check` command, executed during the CI "Lints"
step, to fail with a configuration error. The linter will be unable to correctly load
the Next.js plugin preset, breaking the CI pipeline.
| "version": "0.0.0", | ||
| "devDependencies": { | ||
| "@next/eslint-plugin-next": "^14.2.7", | ||
| "@next/eslint-plugin-next": "^16.0.0", |
There was a problem hiding this comment.
Bug: Upgrading @next/eslint-plugin-next to v16 is incompatible with the project's legacy .eslintrc.js configuration, which will cause the lint-check command to fail in CI.
Severity: HIGH
Suggested Fix
To resolve this, either migrate the ESLint configuration from the legacy .eslintrc.js to the new eslint.config.js (flat config) format as recommended by Next.js v16, or avoid upgrading @next/eslint-plugin-next until the configuration migration is complete.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: frontends/package.json#L38
Potential issue: The project's `frontends/package.json` is being updated to use
`@next/eslint-plugin-next` version 16. This new version of the plugin is designed for
ESLint's new "flat config" format and is not backward compatible with the legacy
`.eslintrc.js` file used in the project. When the `yarn lint-check` command runs in CI,
ESLint (version 8.57.1) will attempt to load the shareable config
`"plugin:@next/next/recommended"`. However, the v16 plugin likely no longer exports this
in the expected legacy format, which will cause a runtime error during the linting
process and fail the CI build.
This PR contains the following updates:
^14.2.7→^16.0.0Release Notes
vercel/next.js (@next/eslint-plugin-next)
v16.1.6Compare Source
Core Changes
Credits
Huge thanks to @mischnic, @wyattjoh, and @ztanner for helping!
v16.1.5Compare Source
Please refer the following changelogs for more information about this security release:
https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472
https://vercel.com/changelog/summary-of-cve-2026-23864
v16.1.4Compare Source
Core Changes
Credits
Huge thanks to @mischnic for helping!
v16.1.3Compare Source
Core Changes
Credits
Huge thanks to @acdlite and @ijjk for helping!
v16.1.2Compare Source
Core Changes
Credits
Huge thanks to @mischnic for helping!
v16.1.1Compare Source
Core Changes
Credits
Huge thanks to @sokra and @ztanner for helping!
v16.1.0Compare Source
Core Changes
next dev --inspect: #85037b4455a6e-20251027to4f931700-20251029: #85518cacheLifetypes out of the webpack plugin and into the dev bundler directly: #85539'use cache'in page/layout component: #855194f931700-20251029to561ee24d-20251101: #85670'next'plugin: #85749561ee24d-20251101to67f7d47a-20251103: #8576267f7d47a-20251103tof646e8ff-20251104: #85772f646e8ff-20251104todd048c3b-20251105: #85819dd048c3b-20251105tofa50caf5-20251107: #85906'use cache'call stacks: #85966fa50caf5-20251107to52684925-20251110: #8598052684925-20251110to93fc5740-20251113: #8610393fc5740-20251113tofb2177c1-20251114: #86155next devis already running: #86083next analyze: a built-in bundle analyzer for Turbopack: #85915experimental.turbopackClient/ServerSideNestedAsyncChunking: #85827next upgrade: #86120fb2177c1-20251114to0972e239-20251118: #86263next analyze: Make ipv6 server links valid and normalize localhost: #86219detailfield of issues: #86518npxifyarn dlxis not available: #86384'use cache'module to a cache function: #86014setReferenceManifestsSingletoncall: #86574'use cache'runtime errors in production: #865008ac5f4eb-20251119tofd524fe0-20251121: #86473charnot replaced: #86573MappedPagesstructure: #86744?dplquery string for local images (without static import): #86485?dplfor src without protocol: #868367dc903cd-20251203to66ae640b-20251204: #8684366ae640b-20251204to378973b3-20251205: #86852resHeadersin static types: #87145turbopackInferModuleSideEffectsso it is only enabled in canary builds: #87215useSearchParamscan be imported forinstanceofchecks: #87269b45bb335-20251211tof93b9fd4-20251217: #87281Example Changes
with-windicssexample: #81846Misc Changes
opt-level = sfor not frequently used crates: #85426experimental.cacheLife: #85467createSandbox: #85507--debug-build-pathsinstead ofNEXT_PRIVATE_APP_PATHS: #85504completion.rsa bit: #84863maxRetriesandhardErrorparameters: #85536cells are created inresolve_rawto make cell allocation order deterministic.: #85525assert*->waitFor*when the util is not instant: #85450RegExp-like implementations incheck: #85537after()tests: #85566test/integration/in flake detection tests: #85590run-for-changescript: #85619extern crateandmacro_usesyntax: #85778NEXT_TEST_PREFER_OFFLINEininstall-native.mjs: #85850next-core/src/next_client_reference/visit_client_reference.rs: #85843non_operation_vc_strongly_consistentfeature usage from next-api: #85874turbo-tasks-macros-sharedcrate intoturbo-tasks-macros: #85917next.browserWithResponse(): #85911'use cache'functions to reduce function allocations: #85904font-familydeclaration: #85913Auth0Link: #85953cacheLife&cacheTagin client: #85872cacheLife&cacheTag: #85875sharpandunrs-resolver: #83168evaluateto take module_graph: #85971encryptActionBoundArgs/decryptActionBoundArgsimports: #86015layersexperiment flag from next-runtime webpack config: #86126ClonefromEffect: #86110next-data-api-endpointfor Middleware HTTP method tests: #86157||,&&, and??as control flow operators: #85837useActionStatewith'use cache': #86292ignoreScriptsforunrs-resolveron bun: #86324selfarguments: #86231turbo_tasks::persisted_graphmodule: #863290972e239-20251118to8ac5f4eb-20251119: #86351||,&&, and??as control flow operators (#85837)": #86432Debuginstead ofDisplayforValueDebugFormatimpl onRcStr: #86522'use cache': #86499serverExternalPackagesFileSystemPath::try_join: #86523Configuration
📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.