Bump eslint-plugin-jest from 28.6.0 to 29.11.2 #3327
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps eslint-plugin-jest from 28.6.0 to 29.11.2.
Release notes
Sourced from eslint-plugin-jest's releases.
... (truncated)
Changelog
Sourced from eslint-plugin-jest's changelog.
... (truncated)
Commits
1835f85chore(release): 29.11.2 [skip ci]b164700fix(prefer-mock-return-shorthand): don't report mutable implementations (#1908)f6145b4ci: include rules that require type-checking in smoke testing (#1903)0d1174echore: disable upcomingeslint-plugin-eslint-pluginrecommended rules (#1905)7785da6chore: enable upcomingeslint-plugin-eslint-pluginrules as warnings (#1904)f7da2fachore: useeslintv9 by default, and updateeslint-remote-testertoo (#1901)ec0b236chore(deps): lock file maintenance (#1902)f020557chore(release): 29.11.1 [skip ci]3a50b97fix(unbound-method): ignore inline use ofjest.mocked(...)(#1862)3d9a6a7ci: disable rules that require typechecking in smoke test (#1900)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for eslint-plugin-jest since your current version.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)