Published November 21, 2026
Flutter 3.51 Beta Opens the Dart 3.15 Cycle, Days After 3.50 Went Stable
Flutter 3.50 went stable on November 11 with Dart 3.14. On the same day, a beta build labelled 3.51.0-0.1.pre appeared carrying Dart 3.15.0. The gap between a stable release and the next beta branch cut is now measured in hours rather than weeks, and that is the most useful fact in this month's release calendar.
The build's release tracking issue is open in the Flutter repository, tied to the flutter-3.51-candidate.0 branch, and it is the first branching of the 3.51 line. There is no published what's new page for 3.51 yet. The documentation site still points at 3.50, and the previous release notes page is the only complete account of the framework's current shape. Anyone quoting a 3.51 feature list this week is quoting a branch, not a release.
Why a beta cut this close to stable is normal now
Flutter moved to four stable releases a year, which means each release line is only in the oven for a quarter. A branch has to be cut almost immediately after the previous stable ships if the next beta is going to have enough time to soak. The 3.50 line got a hotfix on November 19, so it is still being maintained in parallel with the new beta. Both things being true at once is the design, not a schedule slipping.
What that means in practice:
- Stable stays on 3.50 and continues to receive hotfixes, most recently 3.50.1 on November 19.
- Beta moves to 3.51 with Dart 3.15, and will get its own patch stream as bugs surface.
- Release notes for 3.51 land closer to the stable date, not at the branch cut.
The beta channel is therefore a preview of a release whose contents are only partly known. Dart 3.15 exists, its SDK is downloadable, and packages can be tested against it. What the next Flutter stable will actually promise is documented later, which is why beta users tend to be package maintainers and teams with a specific blocking issue rather than application teams.
What the 3.51 line is likely to carry
The trajectory from 3.50 is legible even without release notes. The 3.50 release made direct native interop stable through FFIgen and JNIgen, pushed Material and Cupertino further toward standalone packages, and improved WebAssembly output on Safari and Firefox. Work that lands in the following release usually continues those threads: more polish on interop, further movement of design system code out of the framework, and more of the web toolchain shifted toward Wasm as the default path.
That is a description of direction, not a changelog. The honest position this week is that 3.51 contains a large quantity of merged work that no one has summarised yet, and the parts that matter to a given app will be visible in the breaking change list when it is published. Flutter has also been explicit that breaking changes are batched and announced ahead of a stable release rather than dropped with it, so teams on 3.50 have warning time.
Should you switch to the beta now
For most application teams, no. A beta branch cut ten days ago has had almost no external mileage, and the 3.50 line is still receiving fixes for real regressions, including the asset packaging and Gradle build type failures that 3.50.1 addressed. Moving a production Flutter app to 3.51 in November buys nothing except early exposure to bugs that will be fixed before the stable ships.
There are two exceptions worth naming. Package authors with a plugin that touches platform channels or native interop should be testing against Dart 3.15 now, because their users will hit those changes first. And teams that hit a known fixed issue in 3.51 have a legitimate reason to run the beta in a branch, as long as they can hold that branch while stable catches up.
A useful habit for the next quarter is to keep a beta worktree rather than a beta upgrade. Run the beta SDK from a separate checkout, resolve dependencies there, and let CI build both. That way the beta answers the question you actually have, which is whether your code survives the next release, without turning your daily driver into a test rig. Flutter 3.51 will be stable in a few weeks. The teams that find the breakages before then are the ones that paid attention to a branch cut on a Wednesday rather than a blog post in December.