Four Stable Releases Minimum: Flutter's 2026 Release Cadence
Flutter's 2026 roadmap commits to at least four stable releases for Flutter and Dart, on a predictable quarterly cadence you can plan around.
Published on • October 19, 2026
AI Assistant

The Flutter and Dart 2026 roadmap contains one line that should change how you plan your upgrade schedule for the next twelve months: “We plan a minimum of four stable releases for both Dart and Flutter and 12 beta releases in 2026.” That’s a floor, not a ceiling — but combined with the published branch cutoff dates, it gives you something Flutter releases have rarely offered before: a schedule you can build a real plan around.
What the roadmap actually promises
The roadmap is explicitly aspirational. It says so in its own words: it represents intent gathered primarily from Google-employed contributors, and non-Google contributors now outnumber them. Treat the four-release commitment as a strong signal of cadence, not a contractual guarantee.
That said, the cadence has held so far in 2026:
- Flutter 3.41 — February 11, 2026
- Flutter 3.44 — May 2026 (announced around Google I/O)
- Flutter 3.47 — August 12, 2026
- Flutter 3.50 — expected November 2026
Four stables, roughly one per quarter, matching Flutter’s long-standing “quarterly stable” philosophy described in the repository CHANGELOG.
The roadmap also states that the team is “investing in further test automation to reduce release coordination failures” — a direct response to the times a release cycle has slipped or shipped with regressions. If you maintain a large test suite, that’s the line you care most about.
Branch cutoff dates turn quarters into deadlines
Introduced alongside the 3.41 cycle, Flutter now publishes branch cutoff dates for every stable: the deadline for a pull request to land on the default branch and make the next stable. The 2026 schedule announced with 3.41:
- 3.41 — branched January 6
- 3.44 — branched April 7
- 3.47 — branched July 7
- 3.50 — branches October 6
For you as a consumer of the SDK, cutoff dates matter in two directions. First, if a bug fix you depend on misses the cutoff, it waits a full quarter — so when you evaluate a new stable, check whether your critical fixes actually landed before the branch cut. Second, if you contribute to Flutter, the cutoff is a hard deadline rather than a vague “next release.”
How to plan your upgrades around a quarterly rhythm
A predictable cadence lets you stop treating upgrades as emergency events. A practical pattern:
- Upgrade within the first hotfix window. Stables ship
.0versions; patch releases follow within days to weeks when regressions warrant it (3.47.1 shipped about a week after 3.47.0). Wait for the first patch, then move. - Pin your CI to an exact version. Don’t float on “latest stable” — pin it, and bump deliberately:
# Check what you're running
flutter --version
# Move to a specific stable when you decide to
flutter channel stable
flutter upgrade
- Track the roadmap for breaking changes. The 2026 roadmap’s themes — decoupling Material and Cupertino into standalone packages, completing the Impeller migration on Android, making WebAssembly the default on web — each have direct consequences for your code. The Material/Cupertino decoupling alone means a future stable will deprecate
package:flutter/material.dart’s framework copies in favor of separately versioned packages.
Patch releases are where stability actually lives
The roadmap’s four stable releases are the headline, but the CHANGELOG tells you how Flutter treats stability between them. Flutter ships feature stables quarterly and then hotfixes conservatively — “we only hotfix the latest version,” the policy states, so if you’re on an older stable and hit a bug, the recommended fix is to move to the newest stable line rather than wait for a backport.
That policy has a practical implication for your versioning strategy: staying one patch behind the newest stable is safe, staying one stable behind is increasingly unsupported. Subscribe to the flutter-announce group — hotfixes are announced there before anywhere else.
What four releases a year means for your dependencies
Quarterly stables put steady pressure on the ecosystem, and 2026 is amplifying it:
- Design libraries are splitting out. Material and Cupertino move to standalone packages, so your design dependencies will start versioning independently of the SDK — expect more frequent, smaller updates instead of one giant diff per quarter.
- Plugin authors face a moving floor. AGP 9 support, Swift Package Manager as the iOS/macOS default (3.44+), and minimum-version constraints like
flutter: sdk: ">=3.44"all land on specific stables. A quarterly cadence means your plugins should declare honest Flutter SDK constraints. - Beta releases give you a monthly early read. With 12 beta releases planned across the year, there’s roughly a beta every month to run your test suite against before the stable branch cuts.
If you maintain CI, the cheapest win you can ship this quarter is a scheduled job that runs your full suite against the beta channel weekly and files an issue when something breaks. You’ll find the breakage on your terms instead of during a stable upgrade.
Upgrading
flutter channel stable
flutter upgrade
flutter doctor
Read the roadmap for yourself — it’s short, it’s honest about being aspirational, and it links to the tracking issues for every major theme: Flutter & Dart roadmap on GitHub.