[material_ui, cupertino_ui] Bump Flutter version from to 3.47

[dkwingsmt]

Fixes flutter/flutter#192839

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception 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 which test 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 on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. 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.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[gemini-code-assist]

Code Review

This pull request updates the minimum Flutter framework version from 3.44.0 to 3.47.0 for both the cupertino_ui and material_ui packages, and adds the corresponding pending changelog files. The reviewer feedback recommends changing the version bump type from minor to patch in both changelog files, as bumping the minimum Flutter framework version is classified as a patch change in this repository.

[stuartmorgan-g]

Fixes flutter/flutter#192839

Capturing from offline discussion: this PR doesn't actually fix that issue, it only prevents future versions from having the same issue. If you just land this and do nothing else, everyone on 3.44 will continue to get the last version available to them according to the resolver, which is the one that doesn't work. If the broken versions are retracted on pub, landing this makes sense. If they aren't retracted, you need to do a cycle of:

• revert
• release the revert
• reland with the correct constraint

in which case you won't want to land this PR as-is, because the constraint update will be part of the second PR; landing it first will be one more thing to revert.

[stuartmorgan-g]

If the current broken versions are retracted, to land this without being blocked on flutter/flutter#193032 you can incorporate just a couple of small parts of https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md into this PR:

• The Dart/Flutter version mapping, which is what is breaking presubmit here.
• The version used by the release action so that autorelease doesn't fail in post-submit due to not being able to resolve the 3.47 dependency with the old version (3.44).

[Piinks]

LGTM

[Piinks]

After this lands, I will trigger batch release on both manually.

[auto-submit]

autosubmit label was removed for flutter/packages/12944, because - The status or check suite Dashboard Checks has failed. Please fix the issues identified (or deflake) before re-applying this label.