Update dependency framer-motion to ^11.2.12 - autoclosed

renovate[bot] commented 3 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
framer-motion	`^11.2.11` -> `^11.2.12`

Release Notes

framer/motion (framer-motion)

### [`v11.2.12`](https://togithub.com/framer/motion/blob/HEAD/CHANGELOG.md#11212-2024-06-25) [Compare Source](https://togithub.com/framer/motion/compare/v11.2.11...v11.2.12) ##### Fixed - Fixing `dragConstraints={ref}` mixed with layout animations. ### [`v11.2.11`](https://togithub.com/framer/motion/blob/HEAD/CHANGELOG.md#11211-2024-06-19) [Compare Source](https://togithub.com/framer/motion/compare/v11.2.10...v11.2.11) ##### Fixed - Fix animations in resuspended components.

Configuration

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

🚦 Automerge: Enabled.

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

renovate[bot] commented 3 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-next@14.2.4
npm error Found: eslint@9.5.0
npm error node_modules/eslint
npm error   dev eslint@"9.5.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.5.0
npm error   1 more (eslint-import-resolver-typescript)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.23.0 || ^8.0.0" from eslint-config-next@14.2.4
npm error node_modules/eslint-config-next
npm error   dev eslint-config-next@"14.2.4" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error   peer eslint@"^7.23.0 || ^8.0.0" from eslint-config-next@14.2.4
npm error   node_modules/eslint-config-next
npm error     dev eslint-config-next@"14.2.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-26T02_18_32_794Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-26T02_18_32_794Z-debug-0.log

vercel[bot] commented 3 months ago

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

Name	Status	Preview	Comments	Updated (UTC)
dfweb-v4	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 26, 2024 2:22am

w3bdesign / dfweb-v4