fix(deps): update dependency jquery-migrate to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
jquery-migrate	^1 → ^4.0.0

---

Release Notes

jquery/jquery-migrate (jquery-migrate)

v4.0.2

Compare Source

What's Changed

The 4.0.1 release had missing module files on npm; this release fixes it.

Release

• Build both script & module files on release, fix the map file by @​mgol in #​613

Full Changelog: jquery/jquery-migrate@4.0.1...4.0.2

v4.0.1

Compare Source

What's Changed

This is the first Migrate release meant for jQuery 4.0.0. 🎉

Core

• Prepare for Migrate 4.0.0 by @​mgol in #​555
• Provide a package.json exports setup inspired by jQuery Core by @​mgol in #​566
• Make migrateWarnProp not return the prop for disabled patches by @​mgol in #​571
• Remove compatibility patches needed when upgrading TO jQuery 1.x/2.x by @​mgol in #​555, issue #​549
• Differentiate between compatibility patches and pure warnings by @​mgol in #​555, issue #​472
• Patch & warn against jQuery.now & jQuery.camelCase by @​mgol in #​599

Data

• Patch & warn about props from Object.prototype in data objects by @​mgol in #​561
• Patch $._data as well by @​mgol in #​569

Deferred

• Don't warn on setting getStackHook to the getErrorHook value by @​mgol in #​577

Event

• Patch jQuery.event.global by @​mgol in #​574
• Patch jQuery.event.special's prototype by @​mgol in #​573

Docs

• Improve the solution for boolean-attributes by @​mgol in #​588
• Fix an incorrect warning message & other issues in warnings.md by @​mgol in #​593
• Fix typos, comments, etc. by @​mgol in #​607

Manipulation

• Remove jQuery.UNSAFE_restoreLegacyHtmlPrefilter by @​mgol in #​555, issue #​520

Full Changelog: jquery/jquery-migrate@3.6.0...4.0.1

v4.0.0

Compare Source

v3.6.0

Compare Source

What's Changed

This release prepares jQuery 3.x apps better for a future migration to jQuery 4.x. It also drops support for jQuery 4.x - once you do update to jQuery 4.x, you should load jQuery Migrate 4.x.

Core

• Fill in & warn against $.fn.{push,sort,splice} by @​mgol in #​529
• Fill in & warn against jQuery.proxy by @​mgol in #​530
• Fix the selector module, make CI green by @​mgol in #​552
• Remove support for jQuery 4.x by @​mgol in #​554
• Patch push, sort & splice in jQuery >=3.7.0 by @​mgol in #​568
• Warn against jQuery.now & jQuery.camelCase by @​mgol in #​600

Ajax

• Fill in & warn against automatic JSON-to-JSONP promotion by @​mgol in #​531

Attributes

• Warn & restore boolean attribute & false setter treatment from 3.x by @​mgol in #​540

Data

• Patch camelCase behavior of $.fn.data, warn about Object.prototype by @​mgol in #​559
• Patch $._data & $._removeData as well, add more tests by @​mgol in #​570

Deferred

• Fill in & warn jQuery.Deferred.getStackHook by @​mgol in #​528
• Don't warn on setting getStackHook to the getErrorHook value by @​mgol in #​578

Event

• Patch jQuery.event.special's prototype by @​mgol in #​572

Selector

• Patch & warn against legacy selector pseudos by @​mgol in #​546

Others

• Docs: Add an entry for legacy-self-closed-tags in warnings.md by @​mgol in #​526
• Docs: Tweak README.md & warnings.md - update removal info by @​mgol in #​596
• Docs: Indicate which deprecated APIs are removed in 4.0; tweak a comment by @​mgol in #​606
• Tests: Migrate test runner to jquery-test-runner by @​timmywil in #​560
• Build: Test more browsers and jquery versions in pull requests by @​mgol in #​551

Full Changelog: jquery/jquery-migrate@3.5.2...3.6.0

v3.5.2

Compare Source

This release introduces only one change:

• Make Migrate properly recognized as a CommonJS module in Node.js (#​523, #​525)

Note: you may also find jQuery Migrate 3.5.1 on npm. Do not use it, it's a result of a bad release.

v3.5.1

Compare Source

v3.5.0

Compare Source

Changes:

• Manipulation: Deprecate jQuery.UNSAFE_restoreLegacyHtmlPrefilter (#​518)
• Attributes: Fix compatibility with jQuery 4.x (#​496, #​495)
• Docs: Mark jQuery.fn.load( [ eventData ], handler ) as removed (#​482)
• Replace karma and testswarm with jQuery test runner (#​503 + followups)

v3.4.1

Compare Source

v3.4.0

Compare Source

v3.3.2

Compare Source

v3.3.1

Compare Source

v3.3.0

Compare Source

v3.2.0

Compare Source

v3.1.0

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• 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.

[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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/jquery
npm error   jquery@"^2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jquery@">=4 <5" from [email protected]
npm error node_modules/jquery-migrate
npm error   jquery-migrate@"^4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-05T00_18_43_571Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-05T00_18_43_571Z-debug-0.log