Choose two real stable releases. Boring Doc lists every indexed change between them with its evidence, impact and migration instructions, and can fetch the verified source diff from GitHub.
2361 indexed changes across 37 versions: 10 breaking change, 7 removed, 29 deprecated api, 403 new feature, 616 improvement, 42 performance, 267 platform-specific, 329 developer tooling, 602 bug fix, 56 documentation.
17 high-impact items. Start with: Update semantics header and headingLevel behavior on iOS and Android; OpenGL ES render-to-texture content is stored top-down; Changing RawMenuAnchor close order; ….
Read the 15 official migration guides first, apply `dart fix` where available, then upgrade and run your test suite. Deprecations can be scheduled; removals cannot.
Prefer stepping through stable series sequentially; each breaking-change page has a checklist, before/after code and the official guide. Verify with `flutter analyze`, `flutter test` and a profile-mode run on each target platform.
Tick “Fetch verified source diff” above (or load it now) to corroborate these announcements with the git history between the two tags.
The `header` semantics property now behaves as a no-op on iOS and Android. To declare a section heading for accessibility purposes on these platforms, use the `headingLevel` property with a value greater than `0`.
Impeller's OpenGL ES backend now stores render-to-texture content top-down, the same as the Metal and Vulkan backends. A fragment shader or Flutter GPU app that sampled a render-target texture on OpenGL ES and added a vertical flip to compensate for the old bottom-up orientation now renders that content upside down.
Closing a `RawMenuAnchor` now triggers the `onCloseRequested` and `onClose` callbacks for all descendant `RawMenuAnchor`s. The `onCloseRequested` callback is triggered top-down, starting from the triggering `RawMenuAnchor` and moving to its descendants, while the `onClose` callback is triggered bottom-up. If a `RawMenuAnchor` is already closed, calls to `MenuController.close` and `MenuController.closeChildren` don't trigger the `onCloseRequested` callback.
The `IconData` class is now marked as `final`, which prevents it from being implemented or extended. This change is part of an effort to generalize the mechanism for tree-shaking assets and native code.
For apps targeting Android 17 or higher, orientation, resizability, and aspect ratio restrictions no longer apply on displays with width 600dp or greater. This means that `SystemChrome.setPreferredOrientations` is ignored on these devices.
When a widget with a non-transparent background color, such as a `Container` or `ColoredBox` that sets `color`, sits between a `ListTile` and its nearest `Material` ancestor, the framework now reports an error.
`CupertinoPageTransitionsBuilder` has been relocated from `package:material_ui/material_ui.dart` to the Cupertino package, which is now in `package:cupertino_ui/cupertino_ui.dart`.
Flutter 3.39 merges the UI and platform threads by default on Linux.
A `FontWeight` in a text style will also set the weight attribute of variable fonts. It is no longer necessary to separately use `FontVariation` to control the weight of these fonts.
This release updates `package:material_color_utilities` from `v0.11.1` to `0.13.0`. This updated package includes algorithm changes that align with the Material 3 tokens update.
The `describeEnum` method has been removed from the framework because it's redundant with the `name` getter on `Enum` which was introduced in `Dart 2.14`.
Remove use of deprecated copy_trees. (Other changes, by @rmacnak-google).
Remove use of deprecated API related to removal of the VM isolate. (Other changes, by @rmacnak-google).
Remove unnecessary `deprecated` withOpacity in `text_button.0.dart` in examples (Framework, by @AbdeMohlbi).
Remove deprecated activeColor in `dynamic_content_color.0.dart` example (Framework, by @AbdeMohlbi).
Remove deprecated `activeColor` in `decorated_sliver.1.dart` example (Framework, by @AbdeMohlbi).
Remove deprecated `activeColor` in `switch.0.dart` example (Framework, by @AbdeMohlbi).
AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.