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

Replace dependency eslint-plugin-vitest with @vitest/eslint-plugin 1.0.1 #33

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 30, 2024

This PR contains the following updates:

Package Type Update Change
eslint-plugin-vitest devDependencies replacement 0.5.4 -> 1.0.1

This is a special PR that replaces eslint-plugin-vitest with the community suggested minimal stable replacement version.


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (rebase) September 30, 2024 00:37
Copy link
Contributor Author

renovate bot commented Sep 30, 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: @2bad/[email protected]
npm error Found: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error   @typescript-eslint/utils@"7.18.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     peer @typescript-eslint/eslint-plugin@"^7.0.1" from [email protected]
npm error     node_modules/eslint-config-love
npm error       dev eslint-config-love@"46.0.0" from the root project
npm error   @typescript-eslint/utils@"7.18.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/type-utils
npm error     @typescript-eslint/type-utils@"7.18.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       peer @typescript-eslint/eslint-plugin@"^7.0.1" from [email protected]
npm error       node_modules/eslint-config-love
npm error         dev eslint-config-love@"46.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @vitest/eslint-plugin@"1.0.1" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error   peerOptional @typescript-eslint/utils@">= 8.0" from @vitest/[email protected]
npm error   node_modules/@vitest/eslint-plugin
npm error     dev @vitest/eslint-plugin@"1.0.1" 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-12-30T03_40_59_240Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-30T03_40_59_240Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 3 times, most recently from 98c8248 to 5d13b29 Compare September 30, 2024 09:36
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 4 times, most recently from df3a6b6 to d835653 Compare October 7, 2024 12:41
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from 8c4019f to 585c502 Compare October 14, 2024 07:58
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 4 times, most recently from 033fbd4 to c9141d7 Compare October 28, 2024 06:16
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 4 times, most recently from 4c596c6 to 713cfe1 Compare November 4, 2024 07:24
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 3 times, most recently from 0c7bf59 to 1c816ce Compare November 11, 2024 09:44
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from aaf6e30 to 4c3289f Compare November 25, 2024 03:50
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from 0102b2e to 3dec0ec Compare December 2, 2024 04:58
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from aafaa4e to 5f91389 Compare December 9, 2024 06:28
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from ddf696c to abb09f2 Compare December 16, 2024 06:57
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from 4f55077 to 07a71af Compare December 23, 2024 06:22
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch from 07a71af to 3044738 Compare December 30, 2024 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants