Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency eslint-plugin-jest to v28 #648

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-jest 27.9.0 -> 28.9.0 age adoption passing confidence

Release Notes

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

v28.9.0

Compare Source

Features

28.8.3 (2024-09-04)

Bug Fixes
  • prefer-importing-jest-globals: don't add imports in the middle of statements (#​1645) (9c4197c)

28.8.2 (2024-09-02)

Performance Improvements
  • prefer-importing-jest-globals: stop collecting import specifiers for no reason (#​1646) (0660242)

28.8.1 (2024-08-29)

Bug Fixes
  • prefer-importing-jest-globals: support typescript-eslint parser (#​1639) (307f6a7)

v28.8.3

Compare Source

Bug Fixes
  • prefer-importing-jest-globals: don't add imports in the middle of statements (#​1645) (9c4197c)

v28.8.2

Compare Source

Performance Improvements
  • prefer-importing-jest-globals: stop collecting import specifiers for no reason (#​1646) (0660242)

v28.8.1

Compare Source

Bug Fixes
  • prefer-importing-jest-globals: support typescript-eslint parser (#​1639) (307f6a7)

v28.8.0

Compare Source

Features
  • import formatting rules from eslint-plugin-jest-formatting (#​1563) (74078ee)

v28.7.0

Compare Source

Features
  • allow [@typescript-eslint](https://redirect.github.com/typescript-eslint) v8 (#​1636) (fb43171)

v28.6.0

Compare Source

Features

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

v28.2.0

Compare Source

Features

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

v28.0.0

Compare Source

Bug Fixes
Features
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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the patch Release with a patch level update label Oct 10, 2024
@renovate renovate bot requested a review from a team as a code owner October 10, 2024 20:01
Copy link
Contributor Author

renovate bot commented Oct 10, 2024

⚠️ 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: @typescript-eslint/[email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   dev @typescript-eslint/parser@"5.62.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/parser@"^8.0.0 || ^8.0.0-alpha.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   peerOptional @typescript-eslint/eslint-plugin@"^6.0.0 || ^7.0.0 || ^8.0.0" from [email protected]
npm ERR!   node_modules/eslint-plugin-jest
npm ERR!     dev eslint-plugin-jest@"28.9.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   peer @typescript-eslint/parser@"^8.0.0 || ^8.0.0-alpha.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     peerOptional @typescript-eslint/eslint-plugin@"^6.0.0 || ^7.0.0 || ^8.0.0" from [email protected]
npm ERR!     node_modules/eslint-plugin-jest
npm ERR!       dev eslint-plugin-jest@"28.9.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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-05T20_02_39_156Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-jest-28.x branch from 4af91bb to 0b42508 Compare November 5, 2024 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Release with a patch level update renovate-deps
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants