chore(deps): bump @vitest/mocker and vitest in /web - #87
Merged
Conversation
Bumps [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker) to 4.1.11 and updates ancestor dependency [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together. Updates `@vitest/mocker` from 4.1.10 to 4.1.11 - [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.11/packages/mocker) Updates `vitest` from 4.1.10 to 4.1.11 - [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.11/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/mocker" dependency-version: 4.1.11 dependency-type: indirect - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
jchable
pushed a commit
that referenced
this pull request
Sep 10, 2026
The repository's default branch is `main`, so dependabot opened its PRs against it while the actual flow is feature -> `dev` -> `main`. `main` trails `dev` by 184 commits, so every dependabot PR was cut from, and tested against, code that stale. PR #85 is the measurement, not the worry: `Microsoft.Agents.AI` 1.19.0 -> 1.20.0 went green against `main`, and retargeting its base to `dev` triggered no re-run at all -- the checks reporting it mergeable had never compiled the code it was about to merge into. It merged only because the merge result was built and tested locally first (1350 passing). `target-branch` removes that manual step rather than leaving it to be remembered. Does not cover security updates: those originate from the repository's dependabot alerts, not from this file, and always open against the default branch. #87 (@vitest/mocker, alert GHSA-82fw-gwwq-j7x9 under web/) is one of those. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
dependabot
Bot
deleted the
dependabot/npm_and_yarn/web/multi-d0c2d048a7
branch
September 10, 2026 12:21
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/mocker to 4.1.11 and updates ancestor dependency vitest. These dependencies need to be updated together.
Updates
@vitest/mockerfrom 4.1.10 to 4.1.11Release notes
Sourced from @vitest/mocker's releases.
Commits
9bd8d46chore: release v4.1.11 (#10995)fe5a11dfix(mocker): restrict redirect mocks to the fs allowlist [backport to v4] (#1...Updates
vitestfrom 4.1.10 to 4.1.11Release notes
Sourced from vitest's releases.
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...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)You can disable automated security fix PRs for this repo from the Security Alerts page.