chore(deps): update dependency eslint-plugin-jest to v28.14.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-jest	29.0.1 -> 28.14.0

---

Release Notes

jest-community/eslint-plugin-jest (eslint-plugin-jest)

v28.14.0

Compare Source

Features

• unbound-method: mark docs.recommended and docs.requiresTypeChecking as deprecated (#​1762) (30440ef)

28.13.5 (2025-06-13)

Bug Fixes

• handle string-based import names when resolving Jest functions (#​1761) (d8b5e0e)

28.13.4 (2025-06-13)

Bug Fixes

• prefer-importing-jest-globals: handle string-based import names (#​1756) (547e67b)

28.13.3 (2025-06-10)

Bug Fixes

• prefer-importing-jest-globals: preserve require property renames (#​1754) (41b9523)

28.13.2 (2025-06-10)

Bug Fixes

• prefer-importing-jest-globals: preserve as imports (#​1753) (3a5af78)

28.13.1 (2025-06-10)

Bug Fixes

• prefer-ending-with-an-expect: don't report on await expect (#​1752) (5e3d687)

v28.13.5

Compare Source

Bug Fixes

• handle string-based import names when resolving Jest functions (#​1761) (d8b5e0e)

v28.13.4

Compare Source

Bug Fixes

• prefer-importing-jest-globals: handle string-based import names (#​1756) (547e67b)

v28.13.3

Compare Source

Bug Fixes

• prefer-importing-jest-globals: preserve require property renames (#​1754) (41b9523)

v28.13.2

Compare Source

Bug Fixes

• prefer-importing-jest-globals: preserve as imports (#​1753) (3a5af78)

v28.13.1

Compare Source

Bug Fixes

• prefer-ending-with-an-expect: don't report on await expect (#​1752) (5e3d687)

v28.13.0

Compare Source

Features

• create new prefer-ending-with-an-expect rule (#​1742) (fe1349b)

v28.12.0

Compare Source

Features

• no-disabled-tests: improve error message and simplify rule (#​1739) (1fb5a4a)

28.11.2 (2025-05-29)

Bug Fixes

• no-commented-out-tests: make message less ambiguous (#​1740) (14c27ab)

28.11.1 (2025-05-27)

Bug Fixes

• no-large-snapshots: use a far better message for when an unexpected snapshot is found (#​1736) (0f5b873)

v28.11.2

Compare Source

Bug Fixes

• no-commented-out-tests: make message less ambiguous (#​1740) (14c27ab)

v28.11.1

Compare Source

Bug Fixes

• no-large-snapshots: use a far better message for when an unexpected snapshot is found (#​1736) (0f5b873)

---

Configuration

📅 Schedule: Branch creation - "every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @scaleleap/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint-plugin-unicorn
npm ERR!   dev eslint-plugin-unicorn@"59.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev eslint-plugin-unicorn@"59.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=9.22.0" from [email protected]
npm ERR!   node_modules/eslint-plugin-unicorn
npm ERR!     dev eslint-plugin-unicorn@"59.0.0" 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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-06-30T15_09_00_063Z-debug-0.log