build(deps-dev): bump vitest from 3.0.9 to 3.2.6 - #1284
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.0.9 to 3.2.6. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.6/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 3.2.6 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c568d7e. Configure here.
| "vite@^5.0.0 || ^6.0.0", vite@^6.2.3: | ||
| "vite@^5.0.0 || ^6.0.0 || ^7.0.0-0": | ||
| version "7.3.5" | ||
| resolved "https://registry.yarnpkg.com/vite/-/vite-7.3.5.tgz#90c2d0b7b94a224e7e7dcf22d2912ff0b5291165" |
There was a problem hiding this comment.
Vite 7 breaks Node 18 tests
High Severity
Bumping vitest to 3.2.6 adds a lock entry that resolves its vite peer to 7.3.5, while the repo still targets Node 18 in engines and CI. Vite 7 requires Node 20.19+ or 22.12+, so yarn test on Node 18 can fail even though the project still declares Node 18 support.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit c568d7e. Configure here.
![semgrep-code-getsentry[bot]](https://avatars.githubusercontent.com/in/1153895?s=60&v=4){kind=small}
| "@vitest/snapshot" "3.0.9" | ||
| "@vitest/spy" "3.0.9" | ||
| "@vitest/utils" "3.0.9" | ||
| vitest@3.2.6: |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 3902 lists a dependency (vitest) with a known Critical severity vulnerability.
ℹ️ Why this matters
Affected versions of vitest are vulnerable to Missing Authorization. When the Vitest UI server is listening, the deprecated isFileServingAllowed check is applied without normalizing the URL before filesystem operations, allowing path traversal that lets an attacker read, write, and execute arbitrary files outside the project directory.
References: GHSA
To resolve this comment:
Check if you run the Vitest UI on Windows, or you expose the Vitest UI server to the network with the --api.host flag or api.host config option.
- If you're affected, upgrade this dependency to at least version 4.1.0 at yarn.lock.
- If you're not affected, comment
/fp we don't use this [condition]
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
|
superseded by getsentry/sentry-javascript#22643 |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
1 participant
Bumps vitest from 3.0.9 to 3.2.6.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
b6d56f8chore: release v3.2.616f120dfix: pin last supported vite-node version2cbad0achore: release v3.2.5385a1aefix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...af88b1ffeat(api): addallowWriteandallowExecoptions toapi[backport to v3]...c666d14chore: release v3.2.48a18c8efix(cli): throw error when--shard x/\<count>exceeds count of test files (#...8abd7ccchore(deps): updatetinypool(#8174)93f3200fix(deps): update all non-major dependencies (#8123)0c3be6ffix(coverage): ignore SCSS in browser mode (#8161)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.
You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.