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

chore(deps): update dependency eslint-plugin-jest to v28 #65

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

tradeshift-renovate[bot]
Copy link

@tradeshift-renovate tradeshift-renovate bot commented Apr 6, 2024

This PR contains the following updates:

Package Type Update Change
eslint-plugin-jest devDependencies major ^27.9.0 -> ^28.9.0

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: Enabled.

♻️ Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@tradeshift-renovate
Copy link
Author

tradeshift-renovate bot commented Apr 6, 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^5.62.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @typescript-eslint/eslint-plugin@"^6.0.0 || ^7.0.0 || ^8.0.0" from [email protected]
npm error node_modules/eslint-plugin-jest
npm error   dev eslint-plugin-jest@"^28.9.0" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   peerOptional @typescript-eslint/eslint-plugin@"^6.0.0 || ^7.0.0 || ^8.0.0" from [email protected]
npm error   node_modules/eslint-plugin-jest
npm error     dev eslint-plugin-jest@"^28.9.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-20T09_37_45_033Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-20T09_37_45_033Z-debug-0.log

@tradeshiftcicomponents tradeshiftcicomponents force-pushed the main branch 2 times, most recently from 12a7835 to ba9bfe5 Compare April 21, 2024 00:22
@tradeshiftcicomponents tradeshiftcicomponents force-pushed the main branch 2 times, most recently from cf537ed to 1e337f3 Compare June 16, 2024 00:24
@tradeshiftcicomponents tradeshiftcicomponents force-pushed the main branch 2 times, most recently from d9a0608 to fdfac90 Compare August 4, 2024 00:25
@tradeshiftcicomponents tradeshiftcicomponents force-pushed the main branch 2 times, most recently from ad388e8 to 6f84a12 Compare August 18, 2024 00:25
@tradeshiftcicomponents tradeshiftcicomponents force-pushed the main branch 2 times, most recently from d79f5fb to da30e56 Compare October 6, 2024 00:28
Jesper Terkelsen and others added 2 commits November 19, 2024 09:16
- mark team ownership in tradeshift
- setup rebase automation
@tradeshift-renovate
Copy link
Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants