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 #39

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.

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-16T09_58_13_221Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-16T09_58_13_221Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 4 times, most recently from fab0f6f to 4198007 Compare October 7, 2024 03:38
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 4 times, most recently from b3d4168 to ef16b54 Compare October 14, 2024 03:20
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 5 times, most recently from aee9d06 to c8f6eb4 Compare October 21, 2024 07:27
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 4 times, most recently from 0223a0f to 4553153 Compare October 28, 2024 15:25
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 3 times, most recently from c603280 to 0a081eb Compare November 11, 2024 03:59
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 4 times, most recently from 90e8bd0 to db0cef9 Compare November 18, 2024 06:04
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 3 times, most recently from 6d0119d to 2949e46 Compare November 25, 2024 08:31
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from a7ae4f5 to caa3b62 Compare December 2, 2024 03:24
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 2 times, most recently from a7939f6 to d6880e7 Compare December 9, 2024 05:18
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch 3 times, most recently from a082c08 to b03108b Compare December 16, 2024 06:08
@renovate renovate bot force-pushed the renovate/eslint-plugin-vitest-replacement branch from b03108b to de15a30 Compare December 16, 2024 09:58
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