[Problem/Bug]: WebView2 Runtime stuck on 137.x while stable is 138.x #5297
Description
What happened?
I've noticed that on multiple systems, the WebView2 Runtime is still at version 137.0.3296.93, even though the latest stable release appears to be 138.0.3351.65.
Is this expected behavior?
Is there a known delay or staged rollout for version 138?
If so, could you clarify when 138.x is expected to be broadly available?
We're particularly interested because it includes a critical fix for WebView2's scrolling mechanism.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
137.0.3296.93
SDK Version
1.0.3344-prerelease
Framework
WinUI3/WinAppSDK
Operating System
Windows 11, Windows 10
OS Version
10.0.19045
Repro steps
.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response