chore(deps-dev): bump vitest from 3.2.4 to 4.0.18#1443
chore(deps-dev): bump vitest from 3.2.4 to 4.0.18#1443dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 to 4.0.18. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.18/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.0.18 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
Bumps vitest from 3.2.4 to 4.0.18.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
4d3e3c6chore: release v4.0.18ea837defeat(experimental): addonModuleRunnerhook toworker.init(#9286)e057281fix: usemeta.urlincreateRequire(#9441)dd54e94chore: release v4.0.1759f92d4fix(fsModuleCache): add importers alongside importedModules (#9423)751364efix(fsModuleCache): don't store importers in cache (#9422)4b67fc2fix: typo in browser.provider error (#9394)40841fffix: handle null options inaddEventHandler#9371 (#9372)200dadbfix(pool): handle worker start failures gracefully (#9337)1500654fix(browser): supportfileParallelismon an instance (#9328)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)