[Announcement] WebView2 Runtime and SDK release cadence updates (starting v152)

[Ju-MsGit]

WebView2 Runtime and SDK release cadence updates (starting v152)

Chromium is moving to a 2-week release cadence starting with Chrome 153 (Stable Sep 8, 2026; see the official announcement). Microsoft Edge is aligning to this rhythm — per the Edge release schedule, the change takes effect from Edge version 152 — and the WebView2 Runtime moves with Edge. The WebView2 Runtime will align to Edge's 2-week release cadence starting with Edge / WV2 v152. This is a release-timing change only — there are no changes to the WebView2 API.

WebView2 SDK releases are also moving away from a fixed monthly cadence and will be published on an as-needed basis. SDK releases are no longer expected to accompany every Runtime release.

Please review the impact on your app and plan accordingly.

Release timeline (tentative)

• Aug 3, 2026 — Last 4-week major version: Edge 151 / WV2 151.
• Aug 24, 2026 — Edge / WV2 152 — first release on the new 2-week cadence.
• Sep 7, 2026 onward — every 2 weeks, in lockstep with Edge.

WebView2 SDK release cadence

• WebView2 SDK releases will be published on an as-needed basis when new APIs, bug fixes, security fixes, or other SDK changes warrant a release.
• A new SDK release is not expected for every Runtime release.
• When published, SDK versions will continue to align with the corresponding Runtime version.

Why we're aligning

• Security velocity — critical Chromium patches reach users up to 2 weeks sooner.
• Lower drift risk — WebView2 ships on the same schedule as the Edge runtime it's built on, so you get one consistent, predictable release train to plan around.
• Smaller, simpler updates — more frequent releases mean each update carries a smaller set of changes, making validation more manageable.

What this means for your app

• Evergreen Runtime (default): no action required — the Runtime keeps updating automatically on your users' machines, now delivering security and platform fixes about twice as often.
• Fixed Version Runtime: you stay in control of when you update, but new major versions arrive about twice as often — plan to validate and pick them up more frequently so you don't fall behind on security fixes.
• WebView2 SDK consumers: SDK releases are now published as needed rather than on a fixed monthly schedule. Applications using WebView2 do not need to expect a new SDK package with every Runtime release.

How to prepare

The Beta validation window is now ~21 days (down from 28+). To stay ahead, we recommend:

• Test with Beta and prerelease — validate your core workflows against the WebView2 preview channels, ideally with automated testing.
• Report regressions early — file issues in the WebView2Feedback repo so we can address them before they reach Stable.

What WebView2 provides to help you prepare

• Preview channels — test your app against the WebView2 Beta and prerelease (Dev/Canary) channels before changes reach Stable. See Prerelease testing. (You can also test on preview Windows builds via the Windows Insider Program.)
• Up-to-date release information — current cadence documentation, the Edge / WebView2 release schedule, release notes, and breaking-change announcements (the Breaking Change–labeled posts in this repo) so you can plan ahead.
• Release notes will continue to be published for Runtime releases. SDK release notes will be published when a new SDK is released.

Share feedback

Have a question or run into a regression? Tell us in the WebView2Feedback repo.