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

chore(deps): update dependency eslint-config-next to v14.2.16 #16

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 8, 2024

This PR contains the following updates:

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

Release Notes

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

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

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!


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.


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

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

Copy link
Contributor Author

renovate bot commented Jul 8, 2024

⚠️ 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: packages/react-app/package-lock.json
npm WARN ignoring workspace config at /tmp/renovate/repos/github/celo-org/socialconnect-template/packages/react-app/.npmrc 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @rainbow-me/[email protected]
npm ERR! node_modules/@rainbow-me/rainbowkit
npm ERR!   @rainbow-me/rainbowkit@"^2.0.7" from [email protected]
npm ERR!   packages/react-app
npm ERR!     [email protected]
npm ERR!     node_modules/react-app
npm ERR!       workspace packages/react-app from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @rainbow-me/rainbowkit@"^1.3.6" from @celo/[email protected]
npm ERR! node_modules/@celo/rainbowkit-celo
npm ERR!   @celo/rainbowkit-celo@"^1.2.0" from [email protected]
npm ERR!   packages/react-app
npm ERR!     [email protected]
npm ERR!     node_modules/react-app
npm ERR!       workspace packages/react-app 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

Copy link

netlify bot commented Jul 8, 2024

Deploy Preview for socialconnect-template failed.

Name Link
🔨 Latest commit 70f8128
🔍 Latest deploy log https://app.netlify.com/sites/socialconnect-template/deploys/671c5a7e49f71a0008fae9eb

@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 6c486ee to 9f7420d Compare July 14, 2024 20:45
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.4 chore(deps): update nextjs monorepo to v14.2.5 Jul 14, 2024
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 9f7420d to f871012 Compare August 25, 2024 05:52
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.5 chore(deps): update nextjs monorepo to v14.2.6 Aug 25, 2024
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from f871012 to b0f418d Compare August 31, 2024 11:34
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.6 chore(deps): update nextjs monorepo to v14.2.7 Aug 31, 2024
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.7 chore(deps): update nextjs monorepo to v14.2.8 Sep 8, 2024
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.8 chore(deps): update nextjs monorepo to v14.2.9 Sep 13, 2024
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.9 chore(deps): update nextjs monorepo to v14.2.10 Sep 15, 2024
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.10 chore(deps): update nextjs monorepo to v14.2.11 Sep 16, 2024
@renovate renovate bot changed the title chore(deps): update nextjs monorepo to v14.2.11 chore(deps): update dependency eslint-config-next to v14.2.11 Sep 18, 2024
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v14.2.11 chore(deps): update dependency eslint-config-next to v14.2.12 Sep 21, 2024
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v14.2.12 chore(deps): update dependency eslint-config-next to v14.2.13 Sep 23, 2024
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 50aba75 to 972ea32 Compare October 5, 2024 05:21
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v14.2.13 chore(deps): update dependency eslint-config-next to v14.2.14 Oct 5, 2024
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v14.2.14 chore(deps): update dependency eslint-config-next to v14.2.15 Oct 12, 2024
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-next to v14.2.15 chore(deps): update dependency eslint-config-next to v14.2.16 Oct 26, 2024
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