-
Notifications
You must be signed in to change notification settings - Fork 29.5k
[CP] Flutter analyze --suggestions update for 3.35 #176359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Gradle 9.1.0 was released on 2025-09-18. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [ ] I signed the [CLA]. - [ ] I listed at least one issue that this PR fixes in the description above. - [ ] I updated/added relevant documentation (doc comments with `///`). - [ ] I added new tests to check the change I am making, or this PR is [test-exempt]. - [ ] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord].
…175808) Update the maxKnownAndSupported versions of Java (now 26), AGP (from 8.9.1 to 8.13), and Gradle (now 9.1). Add tests for new codepaths and expand existing test coverage. Some typos and changes to aid debugging included as well. AGP 9 was made available for preview last week https://developer.android.com/build/releases/agp-preview. Fixes: #175669 Commits: - **update max known and supported java, gradle and agp** - **make tests in a loop and add testing for get java version for and validate java and agp** - **move some tests to gradle_utils, make debugging easier** - **Migrated gradle_utils tests from gradle_test to gradle_utils_test** --------- Co-authored-by: Camille Simon <43054281+camsim99@users.noreply.github.com>
This pr assumes #176049 lands first. - **Update java version ranges with the top end limitation for java pre 17** - **change default for unknown agp version to true for java support** - **Add kotlin 2.2* support for analyze --suggestions** - Related to #175669 and #176027 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing.
#176049) Related to #175669 and #176027 - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [ ] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing.
|
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
camsim99
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM let's get this in a hotfix :)
Updates `CHANGELOG` to include the two cherry picks in the 3.35.6 hotfix stable release: #176520 #176359 **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
Fixes #175669
Changelog entry
flutter analyze --suggestionsinclude compatibility info for Gradle 9.1, AGP 9.0, Java 25 and Kotlin 2.2.20 and below.Cherry pick the following prs.
Cherry pick info:
Yes this is covered by tests.
Risk: low, this code is run as part of a seldom used command and any bugs are likely better than false negatives.
Pre-launch Checklist
///).