Skip to content

chore(deps): update dependency @vitest/coverage-v8 to v5 - #239

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) ^3.2.7 → ^5.0.5 age confidence

Release Notes

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

v5.0.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v5.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.0

Compare Source

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes
   🚀 Features

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Pacific/Auckland)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • 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 added the dependencies Pull requests that update a dependency file label Oct 31, 2026
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from afc62f4 to fd6cad8 Compare November 1, 2026 00:56
@renovate

renovate Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: pnpm-lock.yaml
Error: ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION

  × installing dependencies
  ╰─▶ 27 lockfile entries failed verification:
        @rollup/rollup-android-arm-eabi@4.67.3 was published at 2026-10-
      31T19:31:03.557Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-android-arm64@4.67.3 was published at 2026-10-
      31T19:30:43.486Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-android-x64@4.67.3 was published at 2026-10-
      31T19:31:54.916Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-darwin-arm64@4.67.3 was published at 2026-10-
      31T19:30:59.772Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-darwin-x64@4.67.3 was published at 2026-10-
      31T19:36:04.397Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-freebsd-arm64@4.67.3 was published at 2026-10-
      31T19:30:51.720Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-freebsd-x64@4.67.3 was published at 2026-10-
      31T19:32:30.800Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-arm-gnueabihf@4.67.3 was published at 2026-10-
      31T19:31:07.524Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-arm-musleabihf@4.67.3 was published at 2026-10-
      31T19:31:12.783Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-arm64-gnu@4.67.3 was published at 2026-10-
      31T19:30:55.191Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-arm64-musl@4.67.3 was published at 2026-10-
      31T19:30:59.523Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-loong64-gnu@4.67.3 was published at 2026-10-
      31T19:31:20.173Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-loong64-musl@4.67.3 was published at 2026-10-
      31T19:31:23.954Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-ppc64-gnu@4.67.3 was published at 2026-10-
      31T19:31:38.544Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-ppc64-musl@4.67.3 was published at 2026-10-
      31T19:31:43.239Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-riscv64-gnu@4.67.3 was published at 2026-10-
      31T19:31:30.174Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-riscv64-musl@4.67.3 was published at 2026-10-
      31T19:33:16.826Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-s390x-gnu@4.67.3 was published at 2026-10-
      31T19:34:00.592Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-x64-gnu@4.67.3 was published at 2026-10-
      31T19:32:14.413Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        @rollup/rollup-linux-x64-musl@4.67.3 was published at 2026-10-
      31T19:32:38.856Z, within the minimumReleaseAge cutoff (2026-10-
      31T00:56:37.207Z)
        …and 7 more
  help: The lockfile contains entries that the active policies reject. This
        can mean the lockfile is stale, or that someone committed a lockfile
        that bypassed the policy locally — inspect recent changes to pnpm-
        lock.yaml before trusting it. If the changes look expected, run "pnpm
        clean --lockfile" and then "pnpm install" to rebuild from a fresh
        resolution. If the fresh resolution still fails and you trust the
        affected packages, relax the policy that flagged them.


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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants