Update vitest 4.1.6 → 4.1.7 (patch)#90
Conversation
|
|
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.
|
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
@depfu merge |



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.6 → 4.1.7) · Repo
Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)✳️ @vitest/coverage-v8 (4.1.6 → 4.1.7) · Repo
Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)Release Notes
4.1.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release v4.1.7fix(runner): limit concurrency per task branch in addition to per leaf callbacks (backport) (#10384)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