fix(deps): update vitest to v4 to resolve security vulnerabilities#135
Conversation
- vitest: ^1.6.0 → ^4.0.18 - @types/node: ^24.3.0 → ^25.1.0 - typescript: ^5.4.5 → ^5.9.3 Resolves: - GHSA-67mh-4wv8-2f99 (esbuild) - GHSA-93m4-6634-74q7 (vite) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7c5bf3acac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "engines": { | ||
| "node": "^18.0.0 || >=20.0.0" | ||
| "node": "^20.19.0 || >=22.12.0" | ||
| }, |
There was a problem hiding this comment.
Align CI Node version with Vite 7 engine floor
This lockfile update now pulls Vite 7, which declares engines.node as ^20.19.0 || >=22.12.0. The publish workflow still sets node-version: '20' (checked .github/workflows/publish.yml), which resolves to the latest 20.x and can be <20.19 today; in that case npm ci/npm test may fail or Vite/Vitest may refuse to run on CI. Consider bumping CI to 20.19/22.12 or pinning Vite to a version that supports the Node version you’re using.
Useful? React with 👍 / 👎.
Summary
Why
Impact
npm audit: 0 vulnerabilities ✅npm test: 31ファイル / 158テスト全パス ✅npm run build: コンパイル成功 ✅🤖 Generated with Claude Code