Update vitest 4.1.5 → 4.1.6 (patch)#677
Conversation
github-actions
Bot
added
the
size/L
|
Infisical secrets check: ✅ No secrets leaked! 💻 Scan logs2026-05-12T15:55:52Z INF scanning for exposed secrets...
3:55PM INF 591 commits scanned.
2026-05-12T15:55:52Z INF scan completed in 770ms
2026-05-12T15:55:52Z 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
![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]
|
@depfu merge |
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
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.