Bump framer-motion from 6.5.1 to 12.24.0

[dependabot]

Bumps framer-motion from 6.5.1 to 12.24.0.

Changelog

Sourced from framer-motion's changelog.

[12.24.0] 2026-01-05

Added

• { type: "svg" } option to motion.create() for creating custom SVG components.
• px default value type for CSS logical properties (paddingBlock, paddingInline, marginBlock, marginInline).

Fixed

• Ensure drag gesture updates with latest props every render.
• Fix missing JSX import error.
• Fix motion-dom build.
• Exclude src from distributed package.

[12.23.28] 2026-01-05

Fixed

• Fixing MotionStyle type with React 19 when skipLibCheck is false.
• Add guard for process check for better compat with ESM environments.

[12.23.27] 2026-01-05

Fixed

• Improved Intellisense detection for motion import.
• Adding sourcemaps to release.

[12.23.26] 2025-12-10

Fixed

• Moved initialisation of default scale correctors to allow for overwriting existing correctors.

[12.23.25] 2025-12-01

Fixed

• Ensure relative projection boxes are re-measured when parent layout changes.

[12.23.24] 2025-10-10

Fixed

• Ensure that when a component remounts, it continues to fire animations even when initial={false}.

[12.23.23] 2025-10-10

Added

... (truncated)

Commits

• 4f59576 v12.24.0
• 42f0231 Updating changelog
• 2738dba Updating changelog
• f98a283 Fix missing JSX import error in CHANGELOG
• 4388512 Merge pull request #3389 from fxnm/patch-1
• f3924c4 Update CHANGELOG for version 12.24.0
• d53ece5 Merge pull request #3443 from motiondivision/claude/fix-drag-controls-LixiH
• c726ae5 Merge pull request #3430 from reeseo3o/fix/3413-use-transform-logical-properties
• 35ee437 Merge branch 'main' into fix/3413-use-transform-logical-properties
• b93dd50 Merge pull request #3441 from motiondivision/claude/add-svg-type-prop-Wc3de
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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.