as title. This is required due to our policy

context:flutter/flutter#179033

Pre-Review Checklist

• I read theContributor Guide and followed the process outlined there for submitting PRs.
• I read theTree Hygiene page, which explains my responsibilities.
• I read and followed therelevant style guides and ranthe auto-formatter.
• I signed theCLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g.[shared_preferences]
• Ilinked to at least one issue that this PR fixes in the description above.
• I updatedpubspec.yaml with an appropriate new version according to thepub versioning philosophy, or I have commented below to indicate whichversion change exemption this PR falls under¹.
• I updatedCHANGELOG.md to add a description of the change,following repository CHANGELOG style, or I have commented below to indicate whichCHANGELOG exemption this PR falls under¹.
• I updated/added any relevant documentation (doc comments with///).
• I added new tests to check the change I am making, or I have commented below to indicate whichtest exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel onDiscord.

Note: The Flutter team is currently trialing the use ofGemini Code Assist for GitHub. Comments from thegemini-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.