chore(deps-dev): bump vitest from 4.1.2 to 4.1.10 in /apps/web#52
Merged
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
ravirajsinh45
approved these changes
Jul 9, 2026
ravirajsinh45
left a comment
Contributor
There was a problem hiding this comment.
Dependency triage: vitest 4.1.2→4.1.4, dev/test-only patch; the 4.1.3/4.1.4 changes aren't exercised by this jsdom component/store suite. Approving; CI re-runs on rebase.
Contributor
|
@dependabot rebase |
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.2 to 4.1.10. - [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/v4.1.10/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.4 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
83475cc to
97224ba
Compare
This was referenced Jul 9, 2026
ravirajsinh45
added a commit
that referenced
this pull request
Jul 9, 2026
#136) Merging the sibling npm dependabot bumps (#52/#55/#56) via sequential squash without re-rebasing produced a semantically broken pnpm-lock.yaml: git merged the YAML line-by-line with no textual conflict, but tripled several package blocks (picomatch@4.0.5, acorn, agent-base, ...), leaving duplicate mapping keys. pnpm rejects it with ERR_PNPM_BROKEN_LOCKFILE, failing Frontend Build, Lint, and the Docker web image on main (Backend Tests unaffected). Regenerated from package.json with pnpm 10.15 (lockfileVersion 9.0). No package.json or dependency-version changes; verified 'pnpm install --frozen-lockfile' succeeds and the duplicate keys are gone.
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
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.1.2 to 4.1.10.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
db616d2chore: release v4.1.10 (#10718)bae52b5fix(vm): fix external module resolve error with deps optimizer query for enco...a7a61e7chore: release v4.1.9 (#10598)934b0f5fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...7fb2965fix(browser): wait for orchestrator readiness before resolving browser sessio...a518019fix: fiximportOriginalwith optimizer and query import [backport to v4] (#...e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...a09d472chore: release v4.1.7a8fd24cchore: release v4.1.6