chore(deps): update dependency eslint-config-next to v14.2.20

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-next (source)	14.1.4 -> 14.2.20

---

Release Notes

vercel/next.js (eslint-config-next)

v14.2.20

Compare Source

v14.2.19

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• ensure worker exits bubble to parent process (#​73433)
• Increase max cache tags to 128 (#​73125)

Misc Changes

• Update max tag items limit in docs (#​73445)

Credits

Huge thanks to @​ztanner and @​ijjk for helping!

v14.2.18

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Fix: (third-parties) sendGTMEvent not queueing events before GTM init (#​68683) (#​72111)
• Ignore error pages for cache revalidate (#​72412) (#​72484)

Credits

Huge thanks to @​huozhi and @​ijjk for helping!

v14.2.17

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Fix: revert the bad node binary handling (#​72356)
• Ensure pages/500 handles cache-control as expected (#​72050) (#​72110)
• fix unhandled runtime error from generateMetadata in parallel routes (#​72153)

Credits

Huge thanks to @​huozhi, @​ztanner, and @​ijjk for helping!

v14.2.16

Compare Source

v14.2.15

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• support breadcrumb style catch-all parallel routes #​65063
• Provide non-dynamic segments to catch-all parallel routes #​65233
• Fix client reference access causing metadata missing #​70732
• feat(next/image): add support for decoding prop #​70298
• feat(next/image): add images.localPatterns config #​70529
• fix(next/image): handle undefined images.localPatterns config in images-manifest.json
• fix: Do not omit alt on getImgProps return type, ImgProps #​70608
• [i18n] Routing fix #​70761

Credits

Huge thanks to @​ztanner, @​agadzik, @​huozhi, @​styfle, @​icyJoseph and @​wyattjoh for helping!

v14.2.14

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Fix: clone response in first handler to prevent race (#​70082) (#​70649)
• Respect reexports from metadata API routes (#​70508) (#​70647)
• Externalize node binary modules for app router (#​70646)
• Fix revalidateTag() behaviour when invoked in server components (#​70446) (#​70642)
• Fix prefetch bailout detection for nested loading segments (#​70618)
• Add missing node modules to externals (#​70382)
• Feature: next/image: add support for images.remotePatterns.search (#​70302)

Credits

Huge thanks to @​styfle, @​ztanner, @​ijjk, @​huozhi and @​wyattjoh for helping!

v14.2.13

Compare Source

v14.2.12

Compare Source

v14.2.11

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: correct metadata url suffix (https://github.com/vercel/next.js/pull/69959)
• fix: setting assetPrefix to URL format breaks HMR (#​70040)
• Update revalidateTag to batch tags in one request (#​65296)

Credits

Huge thanks to @​huozhi, @​devjiwonchoi, and @​ijjk for helping!

v14.2.10

Compare Source

v14.2.9

Compare Source

v14.2.8

Compare Source

v14.2.7

Compare Source

v14.2.6

Compare Source

v14.2.5

Compare Source

v14.2.4

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: ensure route handlers properly track dynamic access (#​66446)
• fix NextRequest proxy in edge runtime (#​66551)
• Fix next/dynamic with babel and src dir (#​65177)
• Use vercel deployment url for metadataBase fallbacks (#​65089)
• fix(next/image): detect react@19 for fetchPriority prop (#​65235)
• Fix loading navigation with metadata and prefetch (#​66447)
• prevent duplicate RSC fetch when action redirects (#​66620)
• ensure router cache updates reference the latest cache values (#​66681)
• Prevent append of trailing slash in cases where path ends with a file extension (#​66636)
• Fix inconsistency with 404 getStaticProps cache-control (#​66674)
• Use addDependency to track metadata route file changes (#​66714)
• Add timeout/retry handling for fetch cache (#​66652)
• fix: app-router prefetch crash when an invalid URL is passed to Link (#​66755)

Credits

Huge thanks to @​ztanner, @​ijjk, @​wbinnssmith, @​huozhi, and @​lubieowoce for helping!

v14.2.3

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

v14.2.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ai-rsc-demo@0.0.0
npm WARN Found: @vercel/kv@0.2.4
npm WARN node_modules/@vercel/kv
npm WARN   @vercel/kv@"^1.0.0" from the root project
npm WARN   2 more (langchain, @langchain/community)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peerOptional @vercel/kv@"^0.2.3" from langchain@0.1.30
npm WARN node_modules/langchain
npm WARN   langchain@"^0.1.28" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ai-rsc-demo@0.0.0
npm WARN Found: @vercel/kv@0.2.4
npm WARN node_modules/@vercel/kv
npm WARN   @vercel/kv@"^1.0.0" from the root project
npm WARN   2 more (langchain, @langchain/community)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peerOptional @vercel/kv@"^0.2.3" from @langchain/community@0.0.47
npm WARN node_modules/@langchain/community
npm WARN   @langchain/community@"^0.0.47" from the root project
npm WARN   1 more (langchain)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @langchain/community@0.0.47
npm ERR! Found: @vercel/kv@1.0.1
npm ERR! node_modules/@vercel/kv
npm ERR!   @vercel/kv@"^1.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @vercel/kv@"^0.2.3" from @langchain/community@0.0.47
npm ERR! node_modules/@langchain/community
npm ERR!   @langchain/community@"^0.0.47" from the root project
npm ERR!   @langchain/community@"~0.0.41" from langchain@0.1.30
npm ERR!   node_modules/langchain
npm ERR!     langchain@"^0.1.28" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @vercel/kv@0.2.4
npm ERR! node_modules/@vercel/kv
npm ERR!   peerOptional @vercel/kv@"^0.2.3" from @langchain/community@0.0.47
npm ERR!   node_modules/@langchain/community
npm ERR!     @langchain/community@"^0.0.47" from the root project
npm ERR!     @langchain/community@"~0.0.41" from langchain@0.1.30
npm ERR!     node_modules/langchain
npm ERR!       langchain@"^0.1.28" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-24T18_50_39_950Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-24T18_50_39_950Z-debug-0.log

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
freight-search	❌ Failed (Inspect)			Jul 10, 2024 3:48pm
perfreight	❌ Failed (Inspect)			Jul 10, 2024 3:48pm

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add docstrings to all functions and file headers.

This is an automated message generated by Sweep AI.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: ai-rsc-demo@0.0.0
npm error Found: zod@3.22.4
npm error node_modules/zod
npm error   zod@"3.22.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer zod@"^3.23.3" from zod-to-json-schema@3.23.0
npm error node_modules/zod-to-json-schema
npm error   zod-to-json-schema@"3.23.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-04T22_11_39_246Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-04T22_11_39_246Z-debug-0.log

[restack-app]

No applications have been configured for previews targeting branch: main. To do so go to restack console and configure your applications for previews.