Update vitest 4.1.2 → 4.1.3 (patch)#613
Conversation
|
The files' contents are under analysis for test generation. |
|
Infisical secrets check: ✅ No secrets leaked! 💻 Scan logs2026-04-08T11:10:54Z INF scanning for exposed secrets...
11:10AM INF 491 commits scanned.
2026-04-08T11:10:55Z INF scan completed in 368ms
2026-04-08T11:10:55Z INF no leaks found
|
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
@depfu merge |
|
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.
|
|
|
|
Overall Grade |
Security Reliability Complexity Hygiene Coverage |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| Test coverage | Apr 8, 2026 11:10a.m. | Review ↗ | |
| Secrets | Apr 8, 2026 11:10a.m. | Review ↗ | |
| JavaScript | Apr 8, 2026 11:10a.m. | Review ↗ |
Code Coverage Summary
| Language | Line Coverage (Overall) |
|---|---|
| Aggregate | 93.8% |
| Javascript | 93.8% |
➟ Additional coverage metrics may have been reported. See full coverage report ↗
|
Closing because this update has already been applied |



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.2 → 4.1.3) · Repo
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
✳️ @vitest/coverage-v8 (4.1.2 → 4.1.3) · Repo
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
4.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
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