Skip to content

build(deps-dev): bump vitest to 5.0.5 - #318

Merged
MarshallOfSound merged 1 commit into
mainfrom
vitest-5.0.5
Oct 25, 2026
Merged

MarshallOfSound merged 1 commit into
mainfrom
vitest-5.0.5

Conversation

@claude

@claude claude Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Bumps vitest from 5.0.1 to 5.0.5, which also moves the lockfile's @vitest/mocker and @vitest/spy from 5.0.1 to 5.0.5 along with the new versions of vitest's own dependencies: obug 2.2.1 to 3.0.0, why-is-node-running 2.3.0 to 3.2.1 (which drops siginfo and stackback), chai 6.2.2 to 6.3.0, magic-string 1.4.1 to 1.4.3, std-env 4.2.0 to 4.3.0, tinybench 6.1.4 to 6.2.2 and tinyexec 1.3.0 to 1.3.1. All of them were published more than a week ago. 5.0.5 carries the fix for GHSA-p458-7748-mcp3, which affects @vitest/ui and @vitest/browser. This repo doesn't use either package, so it wasn't affected; this just keeps vitest current.


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N2vvE5XzurMvQfsX7Vz7bF
@claude
claude Bot requested a review from a team as a code owner October 22, 2026 22:54
@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedvitest@​5.0.1 ⏵ 5.0.59810079 +199 +1100

View full report

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed this PR and didn't find any bugs. All paths are covered by CODEOWNERS, and the lockfile changes more than the description says, so a quick look from an owner would still help.

What was reviewed:

  • package.json and yarn.lock agree on vitest ^5.0.5. The @ vitest/mocker and @ vitest/spy entries and vitest's own peer pins all move together to 5.0.5.
  • yarn.lock also has two major bumps the description doesn't mention: obug goes from 2.2.1 to 3.0.0, and why-is-node-running goes from ^2.3.0 to an exact 3.2.1. why-is-node-running 3.2.1 drops its siginfo and stackback dependencies. tinybench changes from an exact 6.1.4 to ^6.2.2, and tinyexec 1.3.1 is added. I couldn't check these or the new checksums against the npm registry from here.
  • vite ^8.0.16 still satisfies the peer ranges of vitest and @ vitest/mocker.
Extended reasoning...

The change touches only dev-dependency metadata in package.json and yarn.lock. No runtime or source code changes, and nothing that ships in the published package. It touches no security-sensitive code. What matters most is supply-chain trust in the regenerated lockfile, and I couldn't check it against the registry. I deferred because .github/CODEOWNERS assigns every path to a team, and because the lockfile has transitive major-version bumps (obug 3.x, why-is-node-running 3.x) that the PR description leaves out.

@MarshallOfSound
MarshallOfSound enabled auto-merge (squash) October 25, 2026 22:03
@MarshallOfSound
MarshallOfSound merged commit 9ef0c5b into main Oct 25, 2026
10 checks passed
@MarshallOfSound
MarshallOfSound deleted the vitest-5.0.5 branch October 25, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants