Create changelog entry for flutter 3.35.7#177334
Create changelog entry for flutter 3.35.7#177334auto-submit[bot] merged 1 commit intoflutter:flutter-3.35-candidate.0from
Conversation
|
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. |
There was a problem hiding this comment.
Code Review
This pull request adds a changelog entry for Flutter version 3.35.7. The entry includes two fixes: one for a compile-time failure when extending MenuController, and another that mitigates a memory leak on Android. My review includes a suggestion to format the new entries as a list for consistency and to rephrase one of the descriptions to better align with the project's documentation guidelines for hotfixes.
| [flutter/174082](https://github.com/flutter/flutter/issues/174082) Apps, on all platforms, that extend MenuController class see a compile time failure when building. | ||
| [flutter/173770](https://github.com/flutter/flutter/issues/173770) Mitigates a memory leak that occurs on Android, when `Activities` are not kept upon exit and an Activity is exited and re-entered. |
There was a problem hiding this comment.
There are a couple of improvements for these changelog entries:
- For consistency with the rest of this file, each entry should be a list item starting with a hyphen and a space (
-). - The description for issue
flutter/173770should describe the problem from the user's perspective, rather than the fix, as guided by the project's hotfix documentation best practices. For example, instead of "Mitigates a memory leak...", it could be "A memory leak occurs...".
| [flutter/174082](https://github.com/flutter/flutter/issues/174082) Apps, on all platforms, that extend MenuController class see a compile time failure when building. | |
| [flutter/173770](https://github.com/flutter/flutter/issues/173770) Mitigates a memory leak that occurs on Android, when `Activities` are not kept upon exit and an Activity is exited and re-entered. | |
| - [flutter/174082](https://github.com/flutter/flutter/issues/174082) Apps, on all platforms, that extend MenuController class see a compile time failure when building. | |
| - [flutter/173770](https://github.com/flutter/flutter/issues/173770) A memory leak occurs on Android when `Activities` are not kept upon exit and an Activity is exited and re-entered. |
8784a0b
into
flutter:flutter-3.35-candidate.0
#177334 ## 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]. - [ ] 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.
flutter#177334 ## 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]. - [ ] 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.
Changelog entry onlyl