Update nextjs monorepo to v14.2.1

renovate[bot] commented 6 months ago

This PR contains the following updates:

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

Release Notes

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

### [`v14.2.1`](https://togithub.com/vercel/next.js/compare/v14.2.0...v14.2.1) [Compare Source](https://togithub.com/vercel/next.js/compare/v14.2.0...v14.2.1) ### [`v14.2.0`](https://togithub.com/vercel/next.js/compare/v14.1.4...774563f2b994ae9686b8ec68b506a6ef3d7c9756) [Compare Source](https://togithub.com/vercel/next.js/compare/v14.1.4...v14.2.0)

vercel/next.js (next)

### [`v14.2.1`](https://togithub.com/vercel/next.js/compare/v14.2.0...v14.2.1) [Compare Source](https://togithub.com/vercel/next.js/compare/v14.2.0...v14.2.1) ### [`v14.2.0`](https://togithub.com/vercel/next.js/compare/v14.1.4...774563f2b994ae9686b8ec68b506a6ef3d7c9756) [Compare Source](https://togithub.com/vercel/next.js/compare/v14.1.4...v14.2.0)

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 has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 6 months ago

⚠ 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 ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: my-blog@3.0.0
npm ERR! Found: eslint@9.0.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.23.0 || ^8.0.0" from eslint-config-next@14.2.1
npm ERR! node_modules/eslint-config-next
npm ERR!   dev eslint-config-next@"14.2.1" 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-17T05_07_52_855Z-eresolve-report.txt

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

vercel[bot] commented 6 months ago

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

Name	Status	Preview	Comments	Updated (UTC)
blog-portfolio	❌ Failed (Inspect)			Apr 14, 2024 8:50am

the-coder-o / a-bd.me