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.
21 indexed changes across 7 versions: 4 breaking change, 1 removed, 1 deprecated api, 15 bug fix.
5 high-impact items. Start with: Migrate RawKeyEvent/RawKeyboard system to KeyEvent/HardwareKeyboard system; Default multitouch scrolling; Accessibility traversal order of tooltip changed; ….
Read the 4 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.
A source diff proves code changed; it does not by itself show that a public API is breaking. Use it to corroborate the announcements above.
For some time now (years), Flutter has had two key event systems implemented. The new system reached parity with the old platform-specific raw key event system, and the raw system has been deprecated.
`ScrollBehavior`s now allow or disallow scrolling speeds to be affected by the number of pointers on the screen. `ScrollBehavior.multitouchDragStrategy`, by default, prevents multiple pointers interacting with the scrollable at the same time from affecting the speed of scrolling.
During accessibility focus traversal, `Tooltip.message` is visited immediately after `Tooltip.child`.
Flutter apps included an asset file named `AssetManifest.json`. This file effectively contains a list of assets. Application code can read it using the `AssetBundle` API to determine what assets are available at runtime.
In accordance with Flutter's Deprecation Policy, deprecated APIs that reached end of life after the 3.16 stable release have been removed.
To build a Flutter app for Android, Flutter's Gradle plugins must be applied. Historically, this was done imperatively with Gradle's legacy, imperative apply script method.
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.