Skip to content
Boring Doc

Version Comparison Studio

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.

Categories
Platform
Explain

3.24.5 → 3.27.4Nov 14, 2024 → Feb 5, 2025 · 5 releases in range

Sort:impactversioncategorytopicHide unreviewed
Changes in range
23
Breaking / removed
6
6 with migration guides
Deprecations
0
plan before they are removed
Official evidence
23
6 official migration guide, 17 official changelog

Summary

What changed?

23 indexed changes across 5 versions: 5 breaking change, 1 removed, 17 bug fix.

Will this affect my application?

6 high-impact items. Start with: Color wide gamut support; Component theme normalization; Deep links flag change; ….

What action should I take?

Read the 6 official migration guides first, apply `dart fix` where available, then upgrade and run your test suite. Deprecations can be scheduled; removals cannot.

How do I migrate safely?

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.

What this comparison covers
  • Release-note items are indexed for the most recent series only. For 3.27 this comparison shows official breaking-change guides and hotfix notes.
  • Release-note items are classified from PR titles (heuristic); breaking-change guides are classified from the official index.

Releases in range

  1. 3.27.0
    Dec 11, 2024
    6 changes
  2. 3.27.1
    Dec 16, 2024
    3 changes
  3. 3.27.2
    Jan 13, 2025
    9 changes
  4. 3.27.3
    Jan 21, 2025
    4 changes
  5. 3.27.4
    Feb 5, 2025
    1 changes

Verified source change (GitHub)

Tick “Fetch verified source diff” above (or load it now) to corroborate these announcements with the git history between the two tags.

Changes by category

23 shown

Breaking Breaking change 5

BreakingHigh impact3.27.0 migration guide

Color wide gamut support

The API for the `Color` class in `dart:ui` is changing to support wide gamut color spaces.

Official migration guideVerified classificationFrameworkSource Details
BreakingHigh impact3.27.0 migration guide

Component theme normalization

`CardTheme`, `DialogTheme` and `TabBarTheme` were refactored to conform to Flutter's conventions for component themes. `CardThemeData`, `DialogThemeData`, and `TabBarThemeData` were added to define overrides for the defaults of the component visual properties. Releases of Flutter continue to normalize component themes like these for a more consistent theming experience in the material library.

Official migration guideVerified classificationFrameworkSource Details
BreakingHigh impact3.27.0 migration guide

Deep links flag change

**This breaking change only affects mobile apps that use a third party deep linking plugin package.**

Official migration guideVerified classificationFrameworkSource Details
BreakingHigh impact3.27.0 migration guide

Material 3 Tokens Update in Flutter

The Material Design tokens updated the mapping of 4 color roles in light mode to be more visually appealing while retaining accessible contrast. Testing identified this change as non-breaking in Flutter, but some customers might notice this small change. The update affected the following color properties:

Official migration guideVerified classificationFrameworkSource Details
BreakingHigh impact3.27.0android migration guide

Set default for SystemUiMode to Edge-to-Edge

Edge-to-edge mode is Android's default display behavior as of Android version 15 and above. In Android 15, you could opt out of this behavior but, as of Android 16, you can't. To learn more about this change, check out the Android 16 release notes.

Official migration guideVerified classificationFrameworkSource Details

Removed Removed 1

Bug fix Bug fix 17

AIExplain this upgrade

AI explanationAI-generated · grounded in cited sources
AI explanations are not configured
Set 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.
Was this useful?