Support Flutter 3.47.0 (fix analyze/format CI) - #1088
Open
JSUYA wants to merge 17 commits into
Open
Conversation
Member
Author
|
instead of #1086 |
6 tasks
JSUYA
force-pushed
the
support-flutter-3.47.0
branch
from
August 14, 2026 07:59
68f5f2c to
b1e5144
Compare
Sync with the latest analysis_options.yaml from the flutter/packages repo. Temporarily disable new lints that the existing code does not yet satisfy, marked with "DIFFERENT FROM FLUTTER/PACKAGES: TEMPORARY" comments.
Temporarily suppress new analyze issues in the example via analysis_options.yaml rules instead of modifying the example code copied from upstream.
…47.0 The example code is reformatted with dart format from Flutter 3.47.0 (Dart 3.13.0).
Reformat with dart format from Flutter 3.47.0 (Dart 3.13.0), and remove unused flutter_driver test files in sync with flutter/packages#4347.
Discontinued packages should not be modified. However, flutter pub get run by the tools auto-migrates their analysis_options.yaml since Flutter 3.47.0 (failing the format --fail-on-change check), and new analyzer diagnostics would require code changes in them.
JSUYA
force-pushed
the
support-flutter-3.47.0
branch
from
August 14, 2026 08:09
b1e5144 to
890ed76
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The dart_analyze and format CI jobs have been failing since the stable Flutter 3.47.0 upgrade.
The root analysis_options.yaml is synced with the latest copy from flutter/packages, and the 4 diagnostics newly reported on 3.47.0 (use_super_parameters, collection_methods_unrelated_type, strict_top_level_inference, unintended_html_in_doc_comment) are suppressed with temporary rules marked TEMPORARY instead of code changes, to be re-enabled in per-package follow-up PRs.
The seven directory excludes are pre-applied to the 14 packages that have their own analysis_options.yaml so that the pub get migration becomes a no-op, and for flutter_inappwebview, temporary lint-disabling rules are added to the example's analysis_options.yaml instead of modifying the example code copied from upstream.
The sqflite and video_player packages are reformatted with the output of
dart formatfrom Dart 3.13.0, and video_player's two unused flutter_driver test files are removed in sync with flutter/packages#4347.The CI format check now excludes the discontinued packages, which must not be modified, and the whole change set is verified with Dart 3.13.0 (the same version as CI): all packages pass
dart analyze --fatal-infosand a repo-widedart formatrerun yields zero changes.