Update dependency eslint-plugin-jest to v28

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-jest	28.5.0 -> 28.6.0

---

Release Notes

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

v28.6.0

Compare Source

Features

• prefer-jest-mocked: add new rule (#​1599) (4b6a4f2)
• valid-expect: supporting automatically fixing adding async in some cases (#​1579) (5b9b47e)

v28.5.0

Compare Source

Features

• allow @typescript-eslint/utils v7 as a direct dependency (#​1567) (1476f10)

v28.4.0

Compare Source

Features

• valid-expect: supporting automatically fixing missing await in some cases (#​1574) (a407098)

v28.3.0

Compare Source

Features

• prefer importing jest globals for specific types (#​1568) (c464ae3)

v28.2.0

Compare Source

Features

• support providing aliases for @jest/globals package (#​1543) (744d4f6)

28.1.1 (2024-04-06)

Bug Fixes

• max-expects: properly reset counter when exiting a test case (#​1550) (b4b7cbc)

v28.1.1

Compare Source

Bug Fixes

• max-expects: properly reset counter when exiting a test case (#​1550) (b4b7cbc)

v28.1.0

Compare Source

Features

• add prefer-importing-jest-globals rule (#​1490) (37478d8), closes #​1101

v28.0.0

Compare Source

Bug Fixes

• allow ESLint 9 as peer dependency (#​1547) (3c5e167)
• drop support for Node 19 (#​1548) (c87e388)
• no-large-snapshots: avoid instanceof RegExp check for ESLint v9 compatibility (#​1542) (af4a9c9)

Features

• drop support for @typescript-eslint/eslint-plugin v5 (#​1530) (150e355)
• drop support for Node v14 (#​1527) (df5e580)
• remove no-if rule (#​1528) (f976fc8)
• remove snapshot processor and flat/snapshot config (#​1532) (98087f9)
• upgrade @typescript-eslint/utils to v6 (#​1508) (dc6e8cd)

BREAKING CHANGES

• Node v19 is no longer supported
• removed unneeded snapshot processor and flat/snapshot config
• dropped support for @typescript-eslint/eslint-plugin v5
• dropped support for Node v14
• removed no-if in favor of no-conditional-in-test

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.

[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: pnpm-lock.yaml

Scope: all 21 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
bench/vercel                             |  WARN  deprecated term-size@4.0.0
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@turbo%2Fpack-test-harness: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests

@turbo/pack-test-harness is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c18238b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR