Skip to content

chore(deps): update vitest monorepo to v4.1.5#93

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

chore(deps): update vitest monorepo to v4.1.5#93
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitest-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 21, 2026

This PR contains the following updates:

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

Release Notes

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

v4.1.5

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: (in timezone Africa/Johannesburg)

  • Branch creation
    • At any time (no schedule defined)
  • 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 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 added the renovate label Apr 21, 2026
@socket-security
Copy link
Copy Markdown

socket-security Bot commented Apr 21, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​vitest/​coverage-v8@​4.1.4 ⏵ 4.1.5991007999100
Updated@​vitest/​coverage-istanbul@​4.1.4 ⏵ 4.1.599 +110082 +199100

View full report

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 21, 2026

📚 Docs preview deployed

https://scratchyjs-docs-pr-93.asjas.workers.dev

Updates automatically on every push to this PR.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 21, 2026

⚡ Benchmark Results

benchmarks/renderer/ring-buffer.bench.ts
Suite — Benchmark ops/sec mean (µs) p99 (µs) ±rme vs main
SharedRingBuffer – small payload (64 B) — write 64 bytes 508.2 K 0.0020 0.0070 ±1.54% -6.4%
SharedRingBuffer – small payload (64 B) — write + read 64 bytes 474.7 K 0.0021 0.0070 ±1.49% -9.8%
SharedRingBuffer – medium payload (1 KB) — write 1 KB 311.7 K 0.0032 0.0132 ±0.87% -10.2% ⚠️
SharedRingBuffer – medium payload (1 KB) — write + read 1 KB 248.3 K 0.0040 0.0172 ±0.81% -4.5%
SharedRingBuffer – large payload (16 KB) — write 16 KB 37.3 K 0.0268 0.0466 ±0.60% -36.0% ⚠️
SharedRingBuffer – large payload (16 KB) — write + read 16 KB 116.9 K 0.0086 0.0359 ±1.85% +51.6% 🚀
SharedRingBuffer – sequential throughput (100 × 64 B) — 100 write + read cycles 46.9 K 0.0213 0.0351 ±0.49% +15.4% 🚀
SharedRingBuffer – introspection — availableToRead 14.73 M 0.0001 0.0001 ±0.18% ~0%
SharedRingBuffer – introspection — isEmpty 14.73 M 0.0001 0.0001 ±0.11% ~0%
SharedRingBuffer – introspection — isFull 14.70 M 0.0001 0.0001 ±0.11% ~0%
benchmarks/renderer/shared-buffer.bench.ts
Suite — Benchmark ops/sec mean (µs) p99 (µs) ±rme vs main
SharedBuffer – allocation — createSharedBuffer(4 KB) 609.7 K 0.0016 0.0063 ±0.95% -14.5% ⚠️
SharedBuffer – allocation — createSharedBuffer(64 KB) 48.3 K 0.0207 0.0448 ±0.91% -14.4% ⚠️
SharedBuffer – small payload round-trip — write small JSON 305.9 K 0.0033 0.0110 ±0.42% -14.9% ⚠️
SharedBuffer – small payload round-trip — write + read small JSON 235.9 K 0.0042 0.0121 ±0.43% -13.8% ⚠️
SharedBuffer – medium payload round-trip — write medium JSON (~2 KB) 96.5 K 0.0104 0.0269 ±0.48% +8.4%
SharedBuffer – medium payload round-trip — write + read medium JSON (~2 KB) 57.5 K 0.0174 0.0367 ±0.44% -1.5%
SharedBuffer – large payload round-trip — write large JSON (~10 KB) 16.2 K 0.0617 0.0940 ±0.38% +5.0%
SharedBuffer – large payload round-trip — write + read large JSON (~10 KB) 7.9 K 0.1272 0.1609 ±0.40% ~0%
benchmarks/utils/ip-address.bench.ts
Suite — Benchmark ops/sec mean (µs) p99 (µs) ±rme vs main
getClientIPAddress – no IP headers — no IP-related headers → null 2.69 M 0.0004 0.0007 ±0.72% +1.8%
getClientIPAddress – single header — cf-connecting-ip (Cloudflare) 1.75 M 0.0006 0.0009 ±1.09% +4.5%
getClientIPAddress – single header — x-forwarded-for (simple) 2.03 M 0.0005 0.0009 ±1.40% +5.1%
getClientIPAddress – single header — x-real-ip 1.48 M 0.0007 0.0012 ±0.39% -1.0%
getClientIPAddress – single header — true-client-ip (Akamai / Cloudflare Enterprise) 1.64 M 0.0006 0.0009 ±0.21% +6.3%
getClientIPAddress – x-forwarded-for multi-hop — 2-hop chain 1.94 M 0.0005 0.0008 ±0.32% +11.1% 🚀
getClientIPAddress – x-forwarded-for multi-hop — 4-hop chain 1.77 M 0.0006 0.0009 ±0.33% +6.2%
getClientIPAddress – Forwarded header (RFC 7239) — simple for= directive 957.1 K 0.0010 0.0020 ±2.26% -5.6%
getClientIPAddress – Forwarded header (RFC 7239) — for= with port 720.1 K 0.0014 0.0023 ±0.49% -1.3%
getClientIPAddress – Forwarded header (RFC 7239) — IPv6 literal 729.9 K 0.0014 0.0026 ±0.34% -4.1%
getClientIPAddress – Forwarded header (RFC 7239) — multi-hop Forwarded 801.4 K 0.0012 0.0022 ±2.67% -4.8%
getClientIPAddress – IPv6 addresses — x-forwarded-for IPv6 1.11 M 0.0009 0.0015 ±2.44% -3.5%
benchmarks/utils/promise.bench.ts
Suite — Benchmark ops/sec mean (µs) p99 (µs) ±rme vs main
promiseHash – concurrent resolution — 2 already-resolved promises 819.0 K 0.0012 0.0033 ±0.98% -4.3%
promiseHash – concurrent resolution — 5 already-resolved promises 448.9 K 0.0022 0.0042 ±1.59% -14.3% ⚠️
promiseHash – concurrent resolution — 10 already-resolved promises 270.9 K 0.0037 0.0091 ±1.68% -5.0%
promiseHash – concurrent resolution — 5 promises with object values 434.0 K 0.0023 0.0033 ±1.32% -10.7% ⚠️
timeout – wrapping fast promises — timeout wrapping an already-resolved promise (1 s budget) 892.4 K 0.0011 0.0020 ±0.48% -7.8%
timeout – wrapping fast promises — timeout wrapping an already-resolved object (5 s budget) 838.3 K 0.0012 0.0021 ±1.60% -10.3% ⚠️
benchmarks/utils/safe-redirect.bench.ts
Suite — Benchmark ops/sec mean (µs) p99 (µs) ±rme vs main
safeRedirect – valid paths — root path / 8.04 M 0.0001 0.0002 ±0.13% +18.8% 🚀
safeRedirect – valid paths — simple path /dashboard 4.01 M 0.0002 0.0003 ±0.26% +10.8% 🚀
safeRedirect – valid paths — nested path /settings/profile 3.45 M 0.0003 0.0004 ±0.11% +7.7%
safeRedirect – valid paths — path with query string /search?q=hello 3.74 M 0.0003 0.0003 ±0.20% +7.2%
safeRedirect – valid paths — path with hash /docs#section 3.92 M 0.0003 0.0003 ±0.12% +9.1%
safeRedirect – rejected inputs — absolute URL https://evil.com 4.91 M 0.0002 0.0003 ±0.15% +6.5%
safeRedirect – rejected inputs — protocol-relative URL //evil.com 5.03 M 0.0002 0.0002 ±0.11% +11.7% 🚀
safeRedirect – rejected inputs — backslash-relative /\evil.com 5.01 M 0.0002 0.0002 ±0.11% +8.1%
safeRedirect – rejected inputs — path traversal /../etc/passwd 4.52 M 0.0002 0.0003 ±0.11% +9.8%
safeRedirect – rejected inputs — null input 16.15 M 0.0001 0.0001 ±0.10% ~0%
safeRedirect – rejected inputs — undefined input 16.11 M 0.0001 0.0001 ±0.11% ~0%
safeRedirect – rejected inputs — empty string 16.09 M 0.0001 0.0001 ±0.11% ~0%
safeRedirect – percent-encoded bypass — percent-encoded // (%2F%2F) 4.91 M 0.0002 0.0002 ±0.11% +3.2%
safeRedirect – percent-encoded bypass — percent-encoded path traversal (%2e%2e) 4.84 M 0.0002 0.0002 ±0.29% +2.0%
safeRedirect – percent-encoded bypass — mixed percent-encoded absolute URL 4.61 M 0.0002 0.0003 ±0.32% ~0%
safeRedirect – custom default redirect — valid path with custom default 4.09 M 0.0002 0.0003 ±0.33% +9.3%
safeRedirect – custom default redirect — invalid input with custom default 4.90 M 0.0002 0.0002 ±0.11% +1.9%

🔬 Compared against the latest benchmark run on main. ⚠️ = >10% slower · 🚀 = >10% faster.

@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 39164bc to 327fc27 Compare April 21, 2026 12:05
@renovate renovate Bot assigned Asjas Apr 21, 2026
@renovate renovate Bot force-pushed the renovate/vitest-monorepo branch from 327fc27 to d47ff93 Compare April 29, 2026 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant