Skip to content

chore(deps): update vitest monorepo to v4.1.8#85

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

chore(deps): update vitest monorepo to v4.1.8#85
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Mar 26, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) 4.1.14.1.8 age confidence
vitest (source) 4.1.14.1.8 age confidence

Release Notes

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

v4.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.6

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.1.5

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.3

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.2

Compare Source

This release bumps Vitest's flatted version and removes version pinning to resolve flatted's CVE related issues (#​9975).

   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: (UTC)

  • 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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 force-pushed the renovate/vitest-monorepo branch from 12adbe0 to b035ec2 Compare April 1, 2026 20:37
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4.1.2 chore(deps): update vitest monorepo to v4.1.3 Apr 7, 2026
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 00cced6 to fc38d4f Compare April 9, 2026 11:18
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4.1.3 chore(deps): update vitest monorepo to v4.1.4 Apr 9, 2026
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from fc38d4f to 942c23c Compare April 21, 2026 13:33
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4.1.4 chore(deps): update vitest monorepo to v4.1.5 Apr 21, 2026
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 942c23c to 623c1e8 Compare April 29, 2026 19:11
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 623c1e8 to 520d803 Compare May 11, 2026 16:56
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4.1.5 chore(deps): update vitest monorepo to v4.1.6 May 11, 2026
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 520d803 to bf12aec Compare May 18, 2026 12:53
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4.1.6 chore(deps): update vitest monorepo to v4.1.7 May 20, 2026
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from bf12aec to e48ddd2 Compare May 20, 2026 10:15
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from e48ddd2 to dbc3b34 Compare May 28, 2026 19:45
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to v4.1.7 chore(deps): update vitest monorepo to v4.1.8 Jun 1, 2026
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from dbc3b34 to fbcc113 Compare June 1, 2026 22:34
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from fbcc113 to aff73c3 Compare June 11, 2026 17:05
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