Skip to content

build(deps): bump @vitest/mocker, @vitest/coverage-v8 and vitest in /website - #9567

Merged
iamwhatever merged 1 commit into
mainfrom
dependabot/npm_and_yarn/website/multi-e773253fe8
Sep 16, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
dependabot/npm_and_yarn/website/multi-e773253fe8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 8, 2026

Copy link
Copy Markdown
Contributor

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/mocker from 4.1.10 to 4.1.11

Release notes

Sourced from @​vitest/mocker's releases.

v4.1.11

   🐞 Bug Fixes

    View changes on GitHub
Commits

Updates @vitest/coverage-v8 from 4.1.10 to 4.1.11

Release notes

Sourced from @​vitest/coverage-v8's releases.

v4.1.11

   🐞 Bug Fixes

    View changes on GitHub
Commits

Updates vitest from 4.1.10 to 4.1.11

Release notes

Sourced from vitest's releases.

v4.1.11

   🐞 Bug Fixes

    View changes on GitHub
Commits
  • 9bd8d46 chore: release v4.1.11 (#10995)
  • 9851dbc fix(browser): trigger playwright/chromium gc on lower disk availability [back...
  • See full diff in compare view

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 8, 2026
@dependabot
dependabot Bot requested review from a team and krishdhasmana September 8, 2026 22:30
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Sep 8, 2026
@dwu96 dwu96 added the needs-pr-triage PR scanner: awaiting automated triage label Sep 15, 2026
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Sep 16, 2026
@dwu96 dwu96 added drive-to-green PR claimed by drive-to-green pipeline and removed needs-pr-triage PR scanner: awaiting automated triage labels Sep 16, 2026
@dwu96

dwu96 commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

🤖 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 e489434. The sole blocker is PR Readiness, which is waiting on Internal Content Scan; that gate fails closed with ROLE: and BUCKET: empty ("this run has no credentials for the ruleset"), because a Dependabot-triggered pull_request run receives no repository Actions secrets. CodeQL likewise never starts, same root cause. A re-run cannot clear it — attempt 2 was re-run at 2026-09-16T00:50Z and failed identically, since a re-run inherits the original triggering event's secrets context. Fix plan: rebase onto current main and advance the head as a human actor with a SHA-pinned lease, so the resulting synchronize event re-runs both gates with secrets available (the verified precedent from #7951). The dependency bump itself is not modified.

Note for maintainers: this PR and #9568 carry byte-identical diffs (vitest and @vitest/coverage-v8 4.1.10 → 4.1.11 in website/). Whichever lands first makes the other a no-op that Dependabot will close.

If you'd prefer I don't touch this PR, add the pr-no-autofix label.

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>
@dwu96
dwu96 force-pushed the dependabot/npm_and_yarn/website/multi-e773253fe8 branch from e489434 to 49d4a0c Compare September 16, 2026 01:38
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Sep 16, 2026
@dwu96

dwu96 commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

🤖 Kiro Crew [operator: dwu96#8c08bee0]

Drive-to-green: head advanced via human-actor rebase (no content change).

Every substantive gate was already green on e489434. The sole blocker was PR Readiness waiting on Internal Content Scan (and CodeQL), which fails closed on Dependabot-triggered runs: a Dependabot pull_request event receives no repository Actions secrets, so KIRO_RELEASE_GATE_ROLE_ARN / KIRO_RELEASE_GATE_BUCKET are empty and the added lines are never scanned. Re-running inherits the original event's secrets context and can never pass (attempt 2 of run 34286264194 failed identically).

What I did: rebased this branch onto current main (tip 2b3f9312) and published the rewritten branch with a SHA-pinned lease, as operator dwu96. Old head e489434da → new head 49d4a0c51. The synchronize event from a human actor re-runs the credentialed gates with secrets available — the exact remedy verified on PR #7951.

Content diff: unchanged. Still exactly the Dependabot bump of vitest and @vitest/coverage-v8 4.1.10 → 4.1.11 in website/package.json + website/package-lock.json. No new commit of mine exists (the rebase is the entire change), so no co-author trailer applies. Credit for the content: Dependabot.

Local verification on the rebased head 49d4a0c51:

  • npm ci with Node 24: clean lockfile install
  • tsc -b: clean
  • vitest run (full suite): 2122 files, 34,183 passed / 0 failed (1 expected fail, 2 skipped)

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.

@github-actions

Copy link
Copy Markdown
Contributor

Design Review (Fable 5) — ✅ PASS

Design-level review of 49d4a0c517a9bb08359542bf265c4adf2735c0e8 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Nothing to check.

[DESIGN-REVIEWED] 49d4a0c

@github-actions

Copy link
Copy Markdown
Contributor

UX Review (Fable 5) — ✅ PASS

UX-level review of 49d4a0c517a9bb08359542bf265c4adf2735c0e8 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: PASS

Nothing to check.

[UX-REVIEWED] 49d4a0c

@github-actions

Copy link
Copy Markdown
Contributor

Opus 4.8 Review — ✅ no blocking findings

Reviewed 49d4a0c517a9bb08359542bf265c4adf2735c0e8 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 49d4a0c

Verdict parsed from the review's SHA-scoped output markers for commit 49d4a0c517a9bb08359542bf265c4adf2735c0e8.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 49d4a0c517a9bb08359542bf265c4adf2735c0e8: <one-sentence reason>

@github-actions

Copy link
Copy Markdown
Contributor

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 49d4a0c517a9bb08359542bf265c4adf2735c0e8 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 49d4a0c

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 49d4a0c517a9bb08359542bf265c4adf2735c0e8: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention labels Sep 16, 2026
@dwu96

dwu96 commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

🤖 Kiro Crew [operator: dwu96#8c08bee0]

Flake rerun, no code change. CI run 35044856300 on head 49d4a0c51 completed with exactly one failure: E2E (stub ACP backend, offline) — test_private_workflow_memory.py::test_private_workflows_execute_over_real_projected_mcp failing with RuntimeError: memory_unavailable: cannot verify protected memory hardlinks (operation=entry_stat tree=root_tmp errno=2). This is the known infrastructure flake (same signature previously cleared by rerun, e.g. on the PR #11016 drive), and this PR's diff — a devDependency bump under website/ — cannot reach backend E2E memory code. Issued a targeted --failed rerun of that job only. All five AI review lanes and every other gate are green on this head.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Sep 16, 2026
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention labels Sep 16, 2026
@dwu96

dwu96 commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

🤖 Kiro Crew [operator: dwu96#8c08bee0]

Review-ready. All 83 checks green on head 49d4a0c51, PR Readiness SUCCESS, readiness: passed, MERGEABLE, zero unresolved threads. All five AI review lanes clean (GPT 5.6 and Opus 4.8: no blocking findings; Design and UX: PASS; First Principles: pass with no findings). The E2E (stub ACP backend, offline) memory-hardlink infra flake cleared on the second targeted rerun — main was green on the identical base commit 2b3f9312 throughout, confirming it was never this diff.

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 website/. Auto-merge not armed — landing is a maintainer call. Reminder: sibling #9568 is a byte-identical bump; merging this one makes it a no-op.

@iamwhatever
iamwhatever enabled auto-merge (squash) September 16, 2026 03:06

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@iamwhatever
iamwhatever merged commit 79f2a4a into main Sep 16, 2026
151 of 153 checks passed
@iamwhatever
iamwhatever deleted the dependabot/npm_and_yarn/website/multi-e773253fe8 branch September 16, 2026 03:06
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Sep 16, 2026

@dwu96 dwu96 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 chenmingwei23 removed the drive-to-green PR claimed by drive-to-green pipeline label Sep 16, 2026

@chenmingwei23 chenmingwei23 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

amadsalmon pushed a commit to amadsalmon/KiroCrew that referenced this pull request Sep 22, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants