Bump vitest from 4.0.18 to 4.1.3#5
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
5366d36 to
8de2c89
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
8de2c89 to
af18213
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
af18213 to
6711a55
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
6711a55 to
6cf8752
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
6cf8752 to
4714841
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
4714841 to
74e76cf
Compare
Owner
|
Holding this for a manual upgrade instead of merging as-is. Current CI is failing, and this does not look like a safe standalone Dependabot bump in this repo:
Recommended follow-up is to revisit this as a coordinated testing/tooling update rather than an isolated patch merge. |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
74e76cf to
8dcfa36
Compare
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.0.18 to 4.1.3. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.3/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.3 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vitest-4.1.3
branch
from
8dcfa36 to
907a620
Compare
Contributor
Author
|
Superseded by #19. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps vitest from 4.0.18 to 4.1.3.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
2dc0d62chore: release v4.1.37827363feat: addexperimental.preParseflag (#10070)691d341fix(snapshot): export custom snapshot matcher helper fromvitest(#10042)59b0e64feat(experimental/snapshot): support custom snapshot matcher (#9973)487990afeat(experimental): supportbrowser.locators.exactoption (#10013)146d4f0fix: add@vitest/coverage-v8and@vitest/coverage-istanbulas optional de...3f5bfa3fix: advance fake timers withexpect.pollinterval (#10022)9dbf477fix(vm): fix external module resolve error with deps optimizer query (#10024)ec20455fix(expect): don't leak "runner" types (#10004)66751c9fix(expect): removeJestExtendError.contextfrom verbose error reporting (#...