Skip to content

Update vitest monorepo to ^4.1.11 - #2741

Merged
mergify[bot] merged 2 commits into
mainfrom
renovate/vitest-monorepo
Aug 29, 2026
Merged

Update vitest monorepo to ^4.1.11#2741
mergify[bot] merged 2 commits into
mainfrom
renovate/vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@vitest/coverage-v8 (source) ^4.1.10^4.1.11 age confidence
vitest (source) ^4.1.10^4.1.11 age confidence

Release Notes

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

v4.1.11

Compare Source

   🐞 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 requested a review from cameronraysmith as a code owner August 18, 2026 17:06
@mergify

mergify Bot commented Aug 18, 2026

Copy link
Copy Markdown

Queued — the merge queue status continues in this comment ↓.

@renovate renovate Bot changed the title chore(deps): update vitest monorepo to ^4.1.11 Update vitest monorepo to ^4.1.11 Aug 26, 2026
@renovate renovate Bot changed the title Update vitest monorepo to ^4.1.11 chore(deps): update vitest monorepo to ^4.1.11 Aug 27, 2026
@renovate renovate Bot changed the title chore(deps): update vitest monorepo to ^4.1.11 Update vitest monorepo to ^4.1.11 Aug 29, 2026
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 77a0cac to 1b90404 Compare August 29, 2026 05:46
@mergify mergify Bot added the queued label Aug 29, 2026
@mergify

mergify Bot commented Aug 29, 2026

Copy link
Copy Markdown

Merge Queue Status

  • Entered queue2026-08-29 05:56 UTC · Rule: bot-updates · triggered by rule queue bot PRs
  • 🚫 Left the queue2026-08-29 06:16 UTC · at 9b359f4d212c31111c76eb5b20f89b43735e90ae

This pull request spent 20 minutes 42 seconds in the queue, with no time running CI.

Reason

The pull request conflicts with the base branch

The pull request was held in the queue, conflicting with 1 pull request ahead of it. The conflict became a base branch one after #2675 merged.

Hint

You should update or rebase your pull request.

If you want to requeue this pull request, you can post a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@mergify mergify Bot added dequeued and removed queued labels Aug 29, 2026
@renovate
renovate Bot force-pushed the renovate/vitest-monorepo branch from 9b359f4 to d184c5a Compare August 29, 2026 06:17
@mergify mergify Bot removed the dequeued label Aug 29, 2026
@mergify mergify Bot added the queued label Aug 29, 2026
@mergify

mergify Bot commented Aug 29, 2026

Copy link
Copy Markdown

Merge Queue Status

  • Entered queue2026-08-29 06:29 UTC · Rule: bot-updates · triggered by rule queue bot PRs
  • Checks passed · on draft merge queue: checking #2741 on main (a3ad696) #2876
  • Merged2026-08-29 06:33 UTC · at a636db96dc6f7f3e53a7f596f5d4e5cb40d76c71 · rebase

This pull request spent 4 minutes 11 seconds in the queue, including 35 seconds running CI.

Required conditions to merge
  • all of:
    • check-success=nixbot/nix-build
    • check-success=nixbot/nix-eval
  • any of [🛡 GitHub repository ruleset rule nixbot]:
    • check-success = @sciexp-nixbot/nixbot/nix-build
    • check-neutral = @sciexp-nixbot/nixbot/nix-build
    • check-skipped = @sciexp-nixbot/nixbot/nix-build

@mergify
mergify Bot merged commit a665157 into main Aug 29, 2026
8 checks passed
@mergify
mergify Bot deleted the renovate/vitest-monorepo branch August 29, 2026 06:33
@mergify mergify Bot removed the queued label Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant