[Repo Assist] chore(deps): bundle NuGet updates — GitVersion 6.7.0, Whisper.net.Runtime 1.9.1

[github-actions]

🤖 This PR was created by Repo Assist, an automated AI assistant.

Summary

Bundles three open Dependabot PRs into a single reviewable change:

Package	From	To	Dependabot PR
GitVersion.MsBuild	6.4.0	6.7.0	#621
gitversion.tool	6.4.0	6.7.0	#622
Whisper.net.Runtime	1.9.0	1.9.1	#623

Once merged, maintainers can close the individual Dependabot PRs (#621, #622, #623).

Changes

• src/Directory.Build.props: GitVersion.MsBuild 6.4.0 → 6.7.0 (applies to all source projects via Directory.Build.props)
• .config/dotnet-tools.json: gitversion.tool 6.4.0 → 6.7.0 (local dotnet tool)
• src/OpenClaw.Shared/OpenClaw.Shared.csproj: Whisper.net.Runtime 1.9.0 → 1.9.1

Note: Whisper.net (the managed wrapper) remains at 1.9.0 — only the runtime native package is bumped here, matching what Dependabot proposed (#623).

Test Status

• ✅ dotnet test OpenClaw.Tray.Tests — 934 passed, 2 skipped, 0 failed
• ✅ dotnet test OpenClaw.Shared.Tests — 8 pre-existing failures on master baseline (unrelated, confirmed identical)
• ⚠️ ./build.ps1 — not run (Windows PowerShell build script, unavailable in Linux CI)

---

Generated by 🌈 Repo Assist, see workflow run.

---

Warning

Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.

Protected files

• .config/dotnet-tools.json

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.

Create the pull request manually

# Download the patch from the workflow run
gh run download 27017403097 -n agent -D /tmp/agent-27017403097

# Create a new branch
git checkout -b repo-assist/eng-bundle-nuget-updates-2026-06-05-ca5e8c4b6b9bbe89 master

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-27017403097/aw-repo-assist-eng-bundle-nuget-updates-2026-06-05.patch

# Push the branch and create the pull request
git push origin repo-assist/eng-bundle-nuget-updates-2026-06-05-ca5e8c4b6b9bbe89
gh pr create --title '[Repo Assist] chore(deps): bundle NuGet updates — GitVersion 6.7.0, Whisper.net.Runtime 1.9.1' --base master --head repo-assist/eng-bundle-nuget-updates-2026-06-05-ca5e8c4b6b9bbe89 --repo openclaw/openclaw-windows-node

Generated by 🌈 Repo Assist, see workflow run. Learn more.

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@97143ac59cb3a13ef2a77581f929f06719c7402a

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 5, 2026, 9:45 AM ET / 13:45 UTC.

Summary
Keep open: current master still has all three old dependency versions, and the related Dependabot PRs are open rather than merged. Conservative cleanup should not close this generated bundle issue until maintainers choose the bundle path or land the individual dependency PRs.

Reproducibility: not applicable. this is a dependency-maintenance request, not a runtime bug report. Source inspection confirms the requested versions are not yet present on current master.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
Manual review is the right lane because existing open Dependabot PRs already cover the same bumps and the generated bundle failed to push a protected tool manifest; maintainers should choose bundle versus individual PRs.

Review details

Best possible solution:

Maintainers should choose one canonical path: either create/review the bundled dependency PR from this issue or land the three existing Dependabot PRs individually, with full repository validation before closing the remaining items.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a dependency-maintenance request, not a runtime bug report. Source inspection confirms the requested versions are not yet present on current master.

Is this the best way to solve the issue?

Unclear: a bundle could reduce review overhead, but the same package bumps are already represented by open Dependabot PRs. Maintainers should choose the canonical review path before implementation proceeds.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The requested bundle overlaps three open Dependabot PRs, so creating another branch without a maintainer choice can duplicate review state.
• The generated issue reports partial validation only; any dependency PR still needs the full AGENTS.md build and test pass, including Windows build validation.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 99efc50cbc22.

Label changes

Label changes:

• add P3: This is a low-risk dependency maintenance chore with clear scope and no reported user-facing regression.
• add impact:other: The issue affects build/versioning tooling and the local speech runtime dependency, which is maintainer-visible but outside the specific owned impact categories.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.

Label justifications:

• P3: This is a low-risk dependency maintenance chore with clear scope and no reported user-facing regression.
• impact:other: The issue affects build/versioning tooling and the local speech runtime dependency, which is maintainer-visible but outside the specific owned impact categories.

Evidence reviewed

What I checked:

• Current tool manifest still has gitversion.tool 6.4.0: The repository-local dotnet tool manifest still pins gitversion.tool to 6.4.0, so the tool bump requested here is not on current master. (.config/dotnet-tools.json:6, 99efc50cbc22)
• Current shared build props still has GitVersion.MsBuild 6.4.0: src/Directory.Build.props still references GitVersion.MsBuild version 6.4.0, so the MSBuild package bump is not implemented on current master. (src/Directory.Build.props:16, 99efc50cbc22)
• Current shared project still has Whisper.net.Runtime 1.9.0: OpenClaw.Shared.csproj still pins Whisper.net.Runtime to 1.9.0, so the runtime package bump is not implemented on current master. (src/OpenClaw.Shared/OpenClaw.Shared.csproj:21, 99efc50cbc22)
• Related dependency PRs are open implementation candidates: The provided GitHub context lists open related PRs for the same three dependency bumps: Bump GitVersion.MsBuild from 6.4.0 to 6.7.0 #621, Bump gitversion.tool from 6.4.0 to 6.7.0 #622, and Bump Whisper.net.Runtime from 1.9.0 to 1.9.1 #623. None is merged, so they do not close this issue as implemented.
• Versioning dependency provenance: GitVersion.MsBuild and gitversion.tool are tied to the versioning setup introduced by f8e6ac4d0995e7112f68e9c1766b56361bdaaae0; current docs describe GitVersion as the repository versioning contract. (docs/VERSIONING.md:5, f8e6ac4d0995)
• Speech dependency provenance: Whisper.net.Runtime belongs to the local Whisper STT capability introduced in b0ba9affa25dcc0c5d650253d986be86fd268fb9 and recently touched by speech-input work in 99efc50cbc22f96989958931ef0517e496ec68db. (src/OpenClaw.Shared/OpenClaw.Shared.csproj:21, b0ba9affa25d)

Likely related people:

• Scott Hanselman: Introduced the GitVersion app-version metadata path and the tool/MSBuild package surfaces now targeted by this dependency bump. (role: versioning feature introducer; confidence: medium; commits: f8e6ac4d0995; files: .config/dotnet-tools.json, src/Directory.Build.props, docs/VERSIONING.md)
• Régis Brid: Introduced the Whisper STT/Piper TTS capability and the Whisper.net.Runtime package reference now targeted by this bump. (role: speech feature introducer; confidence: medium; commits: b0ba9affa25d; files: src/OpenClaw.Shared/OpenClaw.Shared.csproj, src/OpenClaw.Shared/Audio/SpeechToTextService.cs, src/OpenClaw.Tray.WinUI/Services/VoiceService.cs)
• Christine Yan: Most recently touched the current dependency files in the localization merge and recently maintained nearby speech-input behavior. (role: recent adjacent contributor; confidence: medium; commits: 85445c78066b, 99efc50cbc22; files: .config/dotnet-tools.json, src/Directory.Build.props, src/OpenClaw.Shared/OpenClaw.Shared.csproj)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[shanselman]

Closing as already completed by the individual dependency PRs:

• Bump GitVersion.MsBuild from 6.4.0 to 6.7.0 #621 bumped GitVersion.MsBuild to 6.7.0
• Bump gitversion.tool from 6.4.0 to 6.7.0 #622 bumped gitversion.tool to 6.7.0
• Bump Whisper.net.Runtime from 1.9.0 to 1.9.1 #623 bumped Whisper.net.Runtime to 1.9.1

Current tree now has the requested versions, so this generated bundle issue is stale.