Repository navigation
build(deps): bump @vitest/mocker, @vitest/coverage-v8 and vitest in /website - #9567
Conversation
|
🤖 Kiro Crew [operator: dwu96#8c08bee0]: This PR has been inactive for 7+ days with failing CI. I've assessed the blockers and they appear resolvable — I'll push fixes directly to this branch as a co-author. Assessment: No real test, lint, or type failures — every substantive gate is green on Note for maintainers: this PR and #9568 carry byte-identical diffs ( If you'd prefer I don't touch this PR, add the |
Bumps [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker) to 4.1.11 and updates ancestor dependencies [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker), [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [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/coverage-v8` 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/coverage-v8) 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/coverage-v8" dependency-version: 4.1.11 dependency-type: direct:development - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
e489434 to
49d4a0c
Compare
|
🤖 Kiro Crew [operator: dwu96#8c08bee0] Drive-to-green: head advanced via human-actor rebase (no content change). Every substantive gate was already green on What I did: rebased this branch onto current Content diff: unchanged. Still exactly the Dependabot bump of Local verification on the rebased head
Note: sibling PR #9568 carries a byte-identical content diff; whichever lands first turns the other into a no-op that Dependabot closes. That resolution is a maintainer call — this drive only advances #9567. |
Design Review (Fable 5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing to check. [DESIGN-REVIEWED] 49d4a0c |
UX Review (Fable 5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing to check. [UX-REVIEWED] 49d4a0c |
Opus 4.8 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 5.6 Review — ✅ no blocking findingsGPT 5.6 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
|
🤖 Kiro Crew [operator: dwu96#8c08bee0] Flake rerun, no code change. CI run 35044856300 on head |
|
🤖 Kiro Crew [operator: dwu96#8c08bee0] Review-ready. All 83 checks green on head Drive summary: the only real blocker was the Internal Content Scan failing closed on Dependabot-triggered runs (no repo secrets in that event context). A human-actor rebase onto main re-fired the credentialed gates, which passed. Content diff untouched from Dependabot's original: vitest + @vitest/coverage-v8 4.1.10 → 4.1.11 in |
iamwhatever
left a comment
There was a problem hiding this comment.
Tier 1 auto-approve: chore / build tooling (2 files). Criteria: no conflict, no requested changes, security path denylist clean, design-doc gate clean, SAST annotations clean, security checklist all-NO, AI reviewers green. Category: Dependabot devDependency bump of vitest, @vitest/mocker and @vitest/coverage-v8 4.1.10 -> 4.1.11 in website/ -- lockfile plus the two package.json devDependency pins, dev-only, no runtime impact.
dwu96
left a comment
There was a problem hiding this comment.
Tier 1 auto-approve: chore / build tooling (2 files). Criteria: no conflict, no requested changes, security path denylist clean, design-doc gate clean, SAST annotations clean, security checklist all-NO, AI reviewers green. Category: devDependency patch bump only — vitest and @vitest/coverage-v8 4.1.10 -> 4.1.11 in website/package.json plus the matching website/package-lock.json entries (transitively es-module-lexer 2.3.1 -> 2.3.2 and vitest's nested picomatch 4.0.5 -> 4.0.7); no runtime dependency and no source change.
chenmingwei23
left a comment
There was a problem hiding this comment.
Tier 1 auto-approve: chore/build (2 files). Criteria: no conflict, no requested changes, security path denylist clean, design-doc gate clean, SAST annotations clean, security checklist all-NO, AI reviewers green. Category: build tooling -- dependabot bump of dev-only vitest packages, no runtime impact.
…odotdev#9567) Bumps [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker) to 4.1.11 and updates ancestor dependencies [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker), [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [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/coverage-v8` 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/coverage-v8) 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/coverage-v8" dependency-version: 4.1.11 dependency-type: direct:development - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps @vitest/mocker to 4.1.11 and updates ancestor dependencies @vitest/mocker, @vitest/coverage-v8 and 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
@vitest/coverage-v8from 4.1.10 to 4.1.11Release notes
Sourced from @vitest/coverage-v8's releases.
Commits
9bd8d46chore: release v4.1.11 (#10995)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.