[wasm] Bump chrome for testing - linux: 146.0.7680.153, windows: 146.0.7680.81

[github-actions]

No description provided.

[dotnet-policy-service]

Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival
See info in area-owners.md if you want to be subscribed.

[github-actions]

🤖 Copilot Code Review — PR #125898

Holistic Assessment

Motivation: Automated Chrome version bump for WASM testing infrastructure. Keeps test browsers current, which is standard maintenance.

Approach: Single-property version string change in eng/testing/BrowserVersions.props — the standard mechanism for this repo.

Summary: ✅ LGTM. Trivial automated version bump — linux_ChromeVersion moves from 146.0.7680.80 → 146.0.7680.153 (patch-level bump within the same Chrome 146 release channel). No code, API, or behavioral changes.

---

Detailed Findings

✅ Correctness — Version bump is well-formed

The effective diff against main is a single line change:

- <linux_ChromeVersion>146.0.7680.80</linux_ChromeVersion>
+ <linux_ChromeVersion>146.0.7680.153</linux_ChromeVersion>

The linux_ChromeRevision, linux_ChromeBaseSnapshotUrl, and linux_V8Version were already updated to the Chrome 146 values by the prior merged PR #125566, so only the patch version needs to advance here. The snapshot URL and revision are consistent.

💡 Title/Content Mismatch — Windows version not updated

The PR title states "windows: 146.0.7680.81" but the diff does not modify any Windows properties — win_ChromeVersion remains at 146.0.7680.66. This is likely just how the automated title is generated (listing latest available versions per platform), but it could be confusing for reviewers expecting a Windows bump as well. Not blocking — just an observation about the bot's title generation.

Generated by Code Review for issue #125898 · ◷