Update vitest 4.1.5 → 4.1.6 (patch)#659
Conversation
|
The files' contents are under analysis for test generation. |
github-actions
Bot
added
the
size/L
|
Infisical secrets check: ✅ No secrets leaked! 💻 Scan logs2026-05-12T15:55:59Z INF scanning for exposed secrets...
3:55PM INF 533 commits scanned.
2026-05-12T15:55:59Z INF scan completed in 425ms
2026-05-12T15:55:59Z INF no leaks found
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.
|
gstraccini
Bot
added
the
☑️ auto-merge
 |
|
Overall Grade |
Security Reliability Complexity Hygiene Coverage |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| Code coverage |  |
May 12, 2026 3:56p.m. | Review ↗ |
| Secrets | |
May 12, 2026 3:56p.m. | Review ↗ |
| JavaScript | |
May 12, 2026 3:56p.m. | Review ↗ |
Code Coverage Summary
| Language | Line Coverage (Overall) |
|---|---|
| Aggregate | 94.1% |
| Javascript | 94.1% |
➟ Additional coverage metrics may have been reported. See full coverage report ↗
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
![gstraccini[bot]](https://avatars.githubusercontent.com/in/480132?s=60&v=4){kind=small}
guibranco
left a comment
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
guibranco
left a comment
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
|
@depfu merge |
1 similar comment
|
@depfu merge |
|
Closing because this update has already been applied |
1 participant
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ vitest (4.1.5 → 4.1.6) · Repo
Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)✳️ @vitest/coverage-v8 (4.1.5 → 4.1.6) · Repo
Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Release Notes
4.1.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.1.6fix(browser): simplify orchestrator otel carrier (#10285)perf: stringify diff objects only once (#10276)feat(browser): provide project reference in `ToMatchScreenshotResolvePath` (#10138)fix: global `sequence.concurrent: true` with top-level `test(..., { concurrent: false })` + depreacte `sequential` test API and options (#10196)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands