Skip to content

Update dependency @vitest/coverage-v8 to v1.6.1 #234

New issue

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

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

Already on GitHub? # to your account

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 10, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-v8 (source) 1.6.0 -> 1.6.1 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v1.6.1

Compare Source

This release includes security patches for:

   🐞 Bug Fixes
    View changes on GitHub

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 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 Feb 10, 2025

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: sql-cursor-pagination@undefined
npm error Found: vitest@1.6.0
npm error node_modules/vitest
npm error   dev vitest@"1.6.0" from the root project
npm error   peer vitest@"1.6.0" from @vitest/browser@1.6.0
npm error   node_modules/@vitest/browser
npm error     peerOptional @vitest/browser@"1.6.0" from vitest@1.6.0
npm error   1 more (@vitest/ui)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"1.6.1" from @vitest/coverage-v8@1.6.1
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"1.6.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 /runner/cache/others/npm/_logs/2025-05-05T07_31_47_309Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-05T07_31_47_309Z-debug-0.log

@github-actions github-actions bot enabled auto-merge February 10, 2025 13:59
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6638494 to 59d53d4 Compare February 11, 2025 11:59
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 59d53d4 to 1bcfb4b Compare February 12, 2025 10:49
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1bcfb4b to 56a24c6 Compare February 12, 2025 21:46
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 56a24c6 to 6cb68eb Compare February 14, 2025 12:25
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6cb68eb to d1bd85f Compare February 14, 2025 18:50
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d1bd85f to 8781679 Compare February 19, 2025 02:38
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8781679 to 62cf747 Compare February 21, 2025 20:09
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 62cf747 to a43768a Compare February 21, 2025 20:11
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a43768a to 506420c Compare February 24, 2025 12:13
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 506420c to 6fa4c49 Compare March 7, 2025 19:33
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6fa4c49 to a1585ff Compare March 9, 2025 06:55
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a1585ff to e9a42d7 Compare March 15, 2025 06:31
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e9a42d7 to c0e4018 Compare March 19, 2025 15:41
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c0e4018 to 7e240d1 Compare March 29, 2025 00:17
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7e240d1 to 17f3abd Compare March 30, 2025 17:31
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 17f3abd to 29e9ef1 Compare April 5, 2025 10:13
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 29e9ef1 to 2db8477 Compare April 12, 2025 11:50
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2db8477 to 9299bc0 Compare April 12, 2025 11:53
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 9299bc0 to 346f92b Compare April 18, 2025 17:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 346f92b to c266cc9 Compare April 19, 2025 23:16
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c266cc9 to 59ff7c9 Compare April 27, 2025 04:12
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 59ff7c9 to b2315d6 Compare May 5, 2025 07:31
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants