Skip to content
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.

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

Update nextjs monorepo to v14.2.23 #838

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-next (source) 14.2.7 -> 14.2.23 age adoption passing confidence
next (source) 14.2.7 -> 14.2.23 age adoption passing confidence

Release Notes

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

v14.2.23

Compare Source

v14.2.22

Compare Source

v14.2.21

Compare Source

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
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
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

vercel/next.js (next)

v14.2.23

Compare Source

v14.2.22

Compare Source

v14.2.21

Compare Source

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

v14.2.17

Compare Source

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

v14.2.10

Compare Source

v14.2.9

Compare Source

v14.2.8

Compare Source


Configuration

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

🚦 Automerge: Enabled.

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 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 renovate bot requested a review from a team as a code owner September 4, 2024 22:55
@renovate renovate bot enabled auto-merge (rebase) September 4, 2024 22:55
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 415663f to 7b4ca7a Compare September 9, 2024 19:45
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.8 Update nextjs monorepo to v14.2.9 Sep 9, 2024
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 7b4ca7a to d4f4381 Compare September 12, 2024 00:06
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.9 Update nextjs monorepo to v14.2.10 Sep 12, 2024
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.10 Update nextjs monorepo to v14.2.11 Sep 12, 2024
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from d4f4381 to cdab1a7 Compare September 12, 2024 22:15
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from cdab1a7 to e6d08a9 Compare September 17, 2024 22:25
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.11 Update nextjs monorepo to v14.2.12 Sep 17, 2024
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.20 Update dependency next to v14.2.20 Dec 8, 2024
@renovate renovate bot changed the title Update dependency next to v14.2.20 Update nextjs monorepo to v14.2.20 Dec 8, 2024
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from a53798d to 7726a43 Compare December 19, 2024 14:19
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.20 Update nextjs monorepo to v14.2.21 Dec 19, 2024
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 7726a43 to dd501f1 Compare December 26, 2024 19:12
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.21 Update nextjs monorepo to v14.2.22 Dec 26, 2024
Copy link

@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from dd501f1 to 88cfa66 Compare January 8, 2025 13:58
@renovate renovate bot changed the title Update nextjs monorepo to v14.2.22 Update nextjs monorepo to v14.2.23 Jan 8, 2025
Copy link
Contributor Author

renovate bot commented Jan 8, 2025

⚠️ 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 ERR! code FETCH_ERROR
npm ERR! errno FETCH_ERROR
npm ERR! invalid json response body at https://registry.npmjs.org/@typescript-eslint%2feslint-plugin reason: Invalid response body while trying to fetch https://registry.npmjs.org/@typescript-eslint%2feslint-plugin: aborted

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-08T13_57_52_107Z-debug-0.log

Copy link

sonarqubecloud bot commented Jan 8, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants