Bump framer-motion from 6.5.1 to 13.0.0

[dependabot]

Bumps framer-motion from 6.5.1 to 13.0.0.

Changelog

Sourced from framer-motion's changelog.

[13.0.0] 2026-08-05

Changed

• Removed optional @emotion/is-prop-valid dependency in favour of explicit <MotionConfig isValidProp={isPropValid}>.

Fixed

• Hardware-accelerated SVG elements correctly apply final style on animation complete.
• AnimatePresence: Ensure nodes are marked as safe to remove when rendering propagate with no motion children.

[12.43.0] 2026-07-27

Added

• Hardware acceleration for backgroundColor in supported browsers.
• Hardware acceleration for SVG elements.

Fixed

• AnimatePresence: Exiting children no longer interleave with entering children, which could reorder and remount children present in both renders.
• motion: Throw error when passing a custom motion component an incorrect ref type.

[12.42.2] 2026-07-01

Fixed

• animateView: Cropped group layers now animate border-radius from the old to new radius.

[12.42.1] 2026-06-30

Fixed

• animateView: Old layer fade out now cancelled when defining .new().

[12.42.0] 2026-06-24

Changed

• animateView: Layers are automatically grouped to match their DOM-hierarchy. New .group(false) method opts-out.

Fixed

• animateView: Auto-crop is now aspect-ratio aware, disabling crops for matching aspect-ratios.
• animateView: Disabled automatic border-radius animation.

[12.41.0] 2026-06-23

Added

... (truncated)

Commits

• e4029ce v13.0.0
• c862954 Updating changelog
• b2bc637 Merge pull request #3781 from motiondivision/fix/3779-svg-duration-zero-indep...
• 96d35b6 Merge pull request #3783 from motiondivision/fix/2652-remove-external-is-vali...
• 165541a Fix #3779: read SVG CSS properties from styles
• e0be524 Fix #2652: scope custom prop validation
• 34058c2 Merge pull request #3784 from motiondivision/fix/3777-empty-propagate
• 0851575 Fix #3777: complete propagated exits without children
• 6acedcc Fix #2652: remove automatic prop validator loading
• 233593b Fix #3779: consolidate SVG style properties
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[shopify-shipitnext]

🔎 View this PR in Shipit Next.

ℹ️ Expand to learn how to deploy and handle emergencies using Shipit Next

Overview

Shipit Next will merge your code on your behalf because this repository uses Shipit Next and its merge queue.

To ship this PR, you can either:

• Comment /shipit to enqueue this PR for merging.
• Go to this PR in Shipit Next and click on the "Ship It" button in the top-right corner.

Comment Commands

• /shipit: Enqueue this PR into the merge queue where it will eventually be merged and deployed.
• /cancel: Eject this PR from the merge queue and rebuild PRs that were enqueued after this PR.
• /shipit --jump-queue: Enqueue this PR at the top of the merge queue where it will be included in the next deploy. Use this for non-emergency situations.
  - Emergency handling procedure for this command can be found here.
• /shipit --emergency: Merge this PR directly into main and deploy to all environments once all require_for_emergency CI checks pass. Please be aware that changes deployed with this command will not be automatically rolled back.
  • Emergency handling procedure for this command can be found here.

Commands exclusive to Deploy Before Merge

• /cancel --emergency: Eject this PR from the merge and rollback any deployments containing this PR.

---

Documentation

• ℹ️ You can read how the merge queue works in Vault here.
• ⚠️ Emergency handling documentation in the Vault describes how to handle emergencies, e.g. failed canaries, broken code in production, etc.

Questions or feedback?

• Non-urgent questions can be submitted in our Discourse.
• Feedback can be submitted in our frustrations Google form.
• If you have feature requests, you may add them or vote for them in our GitHub repository.