Bump vitest from 2.1.9 to 4.1.4#6
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 2.1.9 to 4.1.4. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.4/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.4 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Closing for now. This update is either a failing toolchain major or a higher-risk runtime/release dependency bump, so it should be handled deliberately in a dedicated upgrade pass rather than merged from a Dependabot PR. |
|
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. |
Bumps vitest from 2.1.9 to 4.1.4.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
ac04bacchore: release v4.1.482c858dchore: Remove no-op function in plugin config logic (#8501)d4fbb5cfeat(experimental): support aria snapshot (#9668)b77de96feat(reporter): add filterMeta option to json reporter (#10078)a120e3afeat(experimental): exposeassertionas a public field (#10095)5375780feat(coverage): default to text reporterskipFullif agent detected (#10018)a1b5f0ffix: makeexpect(..., message)consistent as error message prefix (#10068)203f07afix: use "black" foreground for labeled terminal message to ensure contrast (...2dc0d62chore: release v4.1.37827363feat: addexperimental.preParseflag (#10070)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 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)