Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 3, 2025

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) 2.1.8 -> 2.1.9 age confidence

Release Notes

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

v2.1.9

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 - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC).

🚦 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.

@codecov-commenter
Copy link

codecov-commenter commented Feb 3, 2025

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.17%. Comparing base (56f3238) to head (7fd320b).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #75   +/-   ##
=======================================
  Coverage   91.17%   91.17%           
=======================================
  Files           8        8           
  Lines         238      238           
  Branches       62       62           
=======================================
  Hits          217      217           
  Misses         20       20           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from efea9ab to 7fd320b Compare February 4, 2025 03:10
@renovate renovate bot changed the title Update vitest monorepo to v2.1.9 Update dependency @vitest/coverage-v8 to v2.1.9 Feb 4, 2025
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7fd320b to d4a5e94 Compare February 5, 2025 02:54
Copy link
Contributor Author

renovate bot commented Feb 5, 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 cli npm v11.6.1 does not support Node.js v18.20.8. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
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: @opencastsoftware/[email protected]
npm error Found: [email protected]
npm error node_modules/vitest
npm error   dev vitest@"2.1.8" from the root project
npm error   peer vitest@"2.1.8" from @vitest/[email protected]
npm error   node_modules/@vitest/ui
npm error     peerOptional @vitest/ui@"2.1.8" from [email protected]
npm error
npm error Could not resolve dependency:
npm error peer vitest@"2.1.9" from @vitest/[email protected]
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"2.1.9" 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-09-25T18_04_23_135Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-25T18_04_23_135Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from 156f935 to c2ee138 Compare February 13, 2025 01:22
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from d89f8db to 622ce80 Compare February 18, 2025 00:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 8 times, most recently from 5ec623c to 5a6c397 Compare March 7, 2025 00:34
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from e35fe39 to 39f307b Compare March 11, 2025 01:21
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 4900722 to 87bae7d Compare March 23, 2025 01:08
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 7 times, most recently from 357a40c to 90c0c32 Compare June 19, 2025 00:06
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 4f06124 to 26371d3 Compare June 26, 2025 00:53
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 5877724 to 91055b9 Compare July 4, 2025 00:08
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 8 times, most recently from ab77ef9 to c744163 Compare July 12, 2025 00:42
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 7f234cd to 0e3bd21 Compare July 14, 2025 03:58
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from cfc7f11 to 17dd361 Compare August 3, 2025 00:03
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 17dd361 to 10c3d25 Compare August 5, 2025 02:49
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.

1 participant