chore: update dependency eslint-plugin-jest to v27#3349
Merged
escapedcat merged 1 commit intomasterfrom Aug 29, 2022
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR contains the following updates:
^26.0.0->^27.0.0Release Notes
jest-community/eslint-plugin-jest
v27.0.1Compare Source
Bug Fixes
expectcall (#1225) (64ec9c1)v27.0.0Compare Source
Bug Fixes
Features
eslint@6(#1212) (21fc2fe)no-alias-methodsrecommended (#1221) (914b24a)BREAKING CHANGES
no-alias-methodsis now recommended as the methods themselves will be removed in the next major version of Jestno-jest-importruleunbound-methodbase rule are no longer suppressed - really this means that if you don't specifyprojectwhen this rule is enabled and@typescript-eslint/eslint-pluginis 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 presentno-restricted-matchersnow checks against the start of the expect chain, meaning you have to explicitly list each possible matcher & modifier permutations that you want to restrictConfiguration
📅 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.
This PR has been generated by Mend Renovate. View repository job log here.