chore(deps): update dependency lint-staged to v11.2.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lint-staged	11.2.3 -> 11.2.6

---

Release Notes

lint-staged/lint-staged (lint-staged)

v11.2.6

Compare Source

Bug Fixes

• revert back to cosmiconfig from lilconfig (#​1035) (e035b80), closes #​1033 #​981

v11.2.5

Compare Source

Bug Fixes

• correctly import js-yaml to fix yaml config loading (#​1033) (612d806)

v11.2.4

Compare Source

Performance Improvements

• replace cosmiconfig with lilconfig (#​981) (04529e2)

---

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/prisma/ama-prisma/9UKntHK4VAGNtq9tJoQFQEhxBTud
✅ Preview: https://ama-prisma-git-renovate-lint-staged-11x-prisma.vercel.app

[Deployment for 9ceff4e failed]

[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/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/next-auth
npm ERR!   next-auth@"4.0.0-next.26" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer next-auth@">=4" from @next-auth/[email protected]
npm ERR! node_modules/@next-auth/prisma-adapter
npm ERR!   @next-auth/prisma-adapter@"0.5.2-next.15" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/next-auth
npm ERR!   peer next-auth@">=4" from @next-auth/[email protected]
npm ERR!   node_modules/@next-auth/prisma-adapter
npm ERR!     @next-auth/prisma-adapter@"0.5.2-next.15" 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/2022-08-03T15_58_12_416Z-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	Aug 3, 2022 at 4:02PM (UTC)