chore(deps): update dependency eslint-plugin-jest to v27

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-jest	26.6.0 -> 27.0.4

---

Release Notes

jest-community/eslint-plugin-jest

v27.0.4

Compare Source

Bug Fixes

• consistent rule doc notices and sections (#​1226) (2580563)

v27.0.3

Compare Source

Bug Fixes

• ensure jest globals are enabled in styles config (#​1241) (a165e98)

v27.0.2

Compare Source

Bug Fixes

• no-restricted-matchers: improve check to not be solely based on the start of the matcher chain (#​1236) (5fe4568), closes #​1235

v27.0.1

Compare Source

Bug Fixes

• prefer-expect-assertions: report on concise arrow functions with expect call (#​1225) (64ec9c1)

v27.0.0

Compare Source

Bug Fixes

• unbound-method: don't suppress errors from base rule (#​1219) (7c1389e)

Features

• drop support for eslint@6 (#​1212) (21fc2fe)
• drop support for Node versions 12 and 17 (#​1211) (4c987f5)
• make no-alias-methods recommended (#​1221) (914b24a)
• no-jest-import: remove rule (#​1220) (918873b)
• no-restricted-matchers: match based on start of chain, requiring each permutation to be set (#​1218) (f4dd97a)

BREAKING CHANGES

• no-alias-methods is now recommended as the methods themselves will be removed in the next major version of Jest
• no-jest-import: removed no-jest-import rule
• unbound-method: errors thrown by the unbound-method base rule are no longer suppressed - really this means that if you don't specify project when this rule is enabled and @typescript-eslint/eslint-plugin is present, that error will no longer be suppressed instead of silently doing nothing; it will still not throw if this rule is enabled without the base rule being present
• no-restricted-matchers: no-restricted-matchers now checks against the start of the expect chain, meaning you have to explicitly list each possible matcher & modifier permutations that you want to restrict
• Support for ESLint version 6 is removed
• Node versions 12 and 17 are no longer supported

v26.9.0

Compare Source

Features

• create prefer-each rule (#​1222) (574eaed)

26.8.7 (2022-08-21)

Bug Fixes

• prefer-expect-assertions: report on concise arrow functions (#​1207) (f928747)

26.8.6 (2022-08-21)

Bug Fixes

• max-expect: reset expect counter when entering and exiting test function calls (#​1206) (3908ab8)

26.8.5 (2022-08-20)

Bug Fixes

• prefer-expect-assertions: use scoped based jest fn call parser for expect checks (#​1201) (fd54ca1)

26.8.4 (2022-08-19)

Bug Fixes

• prefer-mock-promise-shorthand: ignore mockImplementation functions that have parameters (#​1199) (78ccbef)

26.8.3 (2022-08-15)

Performance Improvements

• cache jest fn call parsing results (#​1187) (525631e)

26.8.2 (2022-08-09)

Bug Fixes

• max-expects: don't count expect.<member>() calls towards max (#​1194) (75a0ff2)

26.8.1 (2022-08-08)

Bug Fixes

• no-standalone-expect: only report on expect.hasAssertions & expect.assertions member calls (#​1191) (4bf9eea)

v26.8.7

Compare Source

Bug Fixes

• prefer-expect-assertions: report on concise arrow functions (#​1207) (f928747)

v26.8.6

Compare Source

Bug Fixes

• max-expect: reset expect counter when entering and exiting test function calls (#​1206) (3908ab8)

v26.8.5

Compare Source

Bug Fixes

• prefer-expect-assertions: use scoped based jest fn call parser for expect checks (#​1201) (fd54ca1)

v26.8.4

Compare Source

Bug Fixes

• prefer-mock-promise-shorthand: ignore mockImplementation functions that have parameters (#​1199) (78ccbef)

v26.8.3

Compare Source

Performance Improvements

• cache jest fn call parsing results (#​1187) (525631e)

v26.8.2

Compare Source

Bug Fixes

• max-expects: don't count expect.<member>() calls towards max (#​1194) (75a0ff2)

v26.8.1

Compare Source

Bug Fixes

• no-standalone-expect: only report on expect.hasAssertions & expect.assertions member calls (#​1191) (4bf9eea)

v26.8.0

Compare Source

Features

• resolve expect based on scope (#​1173) (aa4be21)

v26.7.0

Compare Source

Features

• create prefer-mock-promise-shorthand rule (#​1167) (d965592)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

♻ Rebasing: Whenever PR is behind base branch, 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, click this checkbox.

---

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

Found file in cache: /tmp/containerbase/7576b42decc67f70b61585f41c5074bea75c260886346e567578ea0e0dc2d571/node-v16.17.0-linux-x64.tar.xz

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 27.x releases. However, if you upgrade to 27.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.