Skip to content

build(deps-dev): bump vitest and @vitest/coverage-v8 in /website - #9568

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps vitest and @vitest/coverage-v8. These dependencies needed to be updated together.
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

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

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 patrigao September 8, 2026 22:35
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 8, 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: 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 8713e12. The sole blocker is PR Readiness waiting on Internal Content Scan, which 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. A re-run cannot clear this — 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 force-push with a SHA-pinned lease as a human actor, 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 #9567 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](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8). These dependencies needed to be updated together.

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)

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)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 4.1.11
  dependency-type: direct:development
- dependency-name: "@vitest/coverage-v8"
  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-03a3299ce5 branch from 8713e12 to 845938a Compare September 16, 2026 01:33
@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 action: rebased the branch onto current main and published the rewritten head as a human actor (8713e12 → 845938ae0, lease pinned to the prior tip).

Why: every substantive gate was already green on 8713e12 — the only blocker was Internal Content Scan (run 34286703836) failing closed with empty ROLE:/BUCKET:, plus CodeQL never starting. A Dependabot-triggered pull_request run receives no repository Actions secrets, and a re-run inherits the original trigger's secrets context (attempt 2 failed identically). Advancing the head via a human actor fires a synchronize event whose runs DO get secrets — the same remedy that cleared PR #7951.

Content: zero change. The diff is still exactly the vitest 4.1.10 → 4.1.11 and @vitest/coverage-v8 4.1.10 → 4.1.11 bump (website/package.json + website/package-lock.json). The rebase merged cleanly over main's intervening lockfile changes (e.g. js-yaml 4.3.2 preserved). No new commit was authored, so no co-author trailer applies — the commit remains Dependabot's, credit unchanged.

Local verification on the rebased head:

  • npm ci from the rebased lockfile: clean install (Node 24)
  • tsc -b: clean
  • full frontend suite: 2122 test files, 34,183 tests passed, 0 failures

Verified post-publish: all new workflow runs on 845938ae0 have triggering_actor=dwu96 (human), and Internal Content Scan Gate is running.

@github-actions

Copy link
Copy Markdown
Contributor

Design Review (Fable 5) — ✅ PASS

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

Design-Verdict: PASS

Nothing to check.

[DESIGN-REVIEWED] 845938a

@github-actions

Copy link
Copy Markdown
Contributor

UX Review (Fable 5) — ✅ PASS

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

UX-Verdict: PASS

Nothing to check. Dev-dependency bump (vitest 4.1.10 → 4.1.11) touching only website/package.json and the lockfile — no user-visible control, string, or state changes, so no screenshot evidence is required.

[UX-REVIEWED] 845938a

@github-actions

Copy link
Copy Markdown
Contributor

Opus 4.8 Review — ✅ no blocking findings

Reviewed 845938ae062392b41773a76d569ca8d19a9ce594 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 845938a

Verdict parsed from the review's SHA-scoped output markers for commit 845938ae062392b41773a76d569ca8d19a9ce594.

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

@github-actions

Copy link
Copy Markdown
Contributor

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 845938ae062392b41773a76d569ca8d19a9ce594 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 845938a

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

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Sep 16, 2026
@dwu96

dwu96 commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

🤖 Kiro Crew [operator: dwu96#8c08bee0]

Drive complete — this PR is review-ready. ✅

Final state on head 845938ae0:

  • All 83 checks terminal: 0 failing (PR Readiness passed, readiness: passed)
  • Internal Content Scan Gate: success with credentials populated — the human-actor head advance fixed the Dependabot secrets-context blocker as intended
  • CodeQL: ran and completed (neutral)
  • AI review lanes on this head: GPT 5.6 ✅ no blocking findings · Opus 4.8 ✅ no blocking findings · Design ✅ PASS · UX ✅ PASS · First Principles ✅
  • mergeable: MERGEABLE, zero unresolved review threads
  • No linked issue: this is a routine Dependabot version bump (vitest + @vitest/coverage-v8, 4.1.10 → 4.1.11); there is no tracked issue to close.

No code was changed beyond the rebase — the diff remains exactly Dependabot's original bump. Note for the merging maintainer: sibling PR #9567 carries a byte-identical content diff; whichever lands first makes the other a no-op that Dependabot will close.

Handing off to a human maintainer for merge (auto-merge not armed).

@iamwhatever
iamwhatever enabled auto-merge (squash) September 16, 2026 02: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 dev-dependency bump of vitest and @vitest/coverage-v8 in /website -- website/package.json + website/package-lock.json only, devDependencies, no runtime code path touched.

@iamwhatever
iamwhatever merged commit 1580fc4 into main Sep 16, 2026
83 checks passed
@iamwhatever
iamwhatever deleted the dependabot/npm_and_yarn/website/multi-03a3299ce5 branch September 16, 2026 02: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-only bump of vitest and @vitest/coverage-v8 from 4.1.10 to 4.1.11 in website/package.json plus the matching website/package-lock.json entries — test-runner tooling marked dev:true throughout, no runtime dependency and no source file touched.

@chenmingwei23 chenmingwei23 removed the drive-to-green PR claimed by drive-to-green pipeline label Sep 16, 2026
amadsalmon pushed a commit to amadsalmon/KiroCrew that referenced this pull request Sep 22, 2026
…odotdev#9568)

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8). These dependencies needed to be updated together.

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)

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)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 4.1.11
  dependency-type: direct:development
- dependency-name: "@vitest/coverage-v8"
  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