chore(deps): update dependency eslint-config-next to v11.1.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-next (source)	11.1.2 -> 11.1.4

---

Release Notes

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

v11.1.4

Compare Source

v11.1.3

Compare Source

See https://github.com/vercel/next.js/releases/v12.0.5 for details about this patch.

---

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

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/danieln/ama-prisma/9HTg7aoWyPYmvFNJxjYLQQzEpHQg
✅ Preview: https://ama-prisma-git-renovate-nextjs-monorepo-danieln.vercel.app

[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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: next-auth@4.12.0
npm ERR! Found: next@12.3.4
npm ERR! node_modules/next
npm ERR!   next@"12.3.4" from the root project
npm ERR!   peer next@">=9.0.0" from babel-plugin-superjson-next@0.4.1
npm ERR!   node_modules/babel-plugin-superjson-next
npm ERR!     babel-plugin-superjson-next@"0.4.1" from the root project
npm ERR!   2 more (next-seo, eslint-config-next)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer next@"12.2.5" from next-auth@4.12.0
npm ERR! node_modules/next-auth
npm ERR!   next-auth@"4.12.0" from the root project
npm ERR!   peer next-auth@"^4" from @next-auth/prisma-adapter@1.0.4
npm ERR!   node_modules/@next-auth/prisma-adapter
npm ERR!     @next-auth/prisma-adapter@"1.0.4" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: next@12.2.5
npm ERR! node_modules/next
npm ERR!   peer next@"12.2.5" from next-auth@4.12.0
npm ERR!   node_modules/next-auth
npm ERR!     next-auth@"4.12.0" from the root project
npm ERR!     peer next-auth@"^4" from @next-auth/prisma-adapter@1.0.4
npm ERR!     node_modules/@next-auth/prisma-adapter
npm ERR!       @next-auth/prisma-adapter@"1.0.4" 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/2022-11-22T00_32_05_843Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-22T00_32_05_843Z-debug-0.log

[vercel]

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

Name	Status	Preview	Updated
ama-prisma	✅ Ready (Inspect)	Visit Preview	Nov 22, 2022 at 0:34AM (UTC)