Microsoft WebView2 is Switching to a 2-Week Release Cycle With Version 152

Microsoft is speeding up WebView2 updates, and developers will soon have a much faster release schedule. Starting with version 152, the WebView2 Runtime will move from four-week releases to a two-week cadence.

WebView2 Runtime is getting major updates twice as often

Version 152 will release sometime during the week of August 27. It will be the final major WebView2 release using the current four-week schedule. Things change with version 153, which arrives during the week of September 10. From there, Microsoft plans to release a new major version roughly every two weeks.

The change follows Microsoft Edge’s own move toward a two-week major-release cycle. Microsoft says the faster schedule should deliver security fixes, platform improvements, and other capabilities sooner.

The WebView2 SDK is also changing, although it won’t follow a fixed two-week schedule. Microsoft says SDK releases will arrive when new features, fixes, security updates, or improvements are ready.

What developers need to know before the switch

Developers using the Evergreen Runtime do not need to make changes. Their users will automatically receive the newer runtime releases. Teams using the Fixed Version Runtime will have more control over updates. However, they will need to validate newer versions more frequently to avoid missing security fixes.

Microsoft recommends testing applications through the Microsoft Edge Beta preview channel. Developers can also automate workflow testing using Microsoft Edge WebDriver. Not to forget, Microsoft previously confirmed two-week update release cycle for its in-house Edge browser, too.

The company further says that early testing can help catch application-specific problems before Stable releases. Moreover, developers are also encouraged to report regressions through the WebView2Feedback GitHub repository.

Due to their ease of use, web apps and WebView2 remain popular with developers. However, Microsoft is increasingly shifting toward WinUI for better performance, deeper Windows integration, and a more consistent native experience.