[QuncCccccc]

Does the flutter/core-packages steps of Updating-Packages-repo-for-a-stable-release.md for the 3.50 stable release. This repo wasn't updated for 3.47, so this also catches up on that release:

• Updates the multi-version analysis and test matrix to the Dart versions of flutter/packages' stable, N-1, and N-2 Flutter versions: 3.14.0 (Flutter 3.50.0), 3.13.7 (Flutter 3.47.9), and 3.12.2 (Flutter 3.44.9), plus main. The matrix previously covered only N-1 and stable; this adds N-2 as the doc describes.
• Updates the Windows unit tests and the release action to Dart 3.14.0.
• Raises min_dart to 3.12.0 (the Dart version of Flutter 3.44.0, flutter/packages' new minimum), and updates all packages with update-min-sdk --flutter-min=3.44.0, run with the repo tooling from [ci] Update repo for 3.50 stable release packages#13628, which has the updated version mapping.
• Adds NEXT CHANGELOG entries with update-release-info --version=next (no version bumps, per repo policy).

Additional adjustments needed for CI with the updated versions:

• Applies dart fix --code=prefer_initializing_formals in multicast_dns and mustache_template, whose language version moved to Dart 3.12, adopting private named parameters (this._foo; call-site argument names are unchanged).
• Also removes the outdated "we aren't actually testing N-1 or N-2" note from the min_dart comment in .repo_tool_config.yaml, since the matrix now covers N-1 and N-2.

Companion to flutter/packages#13628.

There's no tracking issue for this routine post-release update.

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 Flutter style guide 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. [vector_math]
• 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. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request updates the minimum supported Dart SDK version from 3.10.0 to 3.12.0 across multiple packages, including updating their pubspec.yaml files, examples, and CHANGELOG.md files, as well as the repository configuration. Feedback suggests updating or removing an outdated comment in .repo_tool_config.yaml regarding legacy version analysis testing.

[gemini-code-assist]

The comment on lines 12-13 states that 'we aren't actually testing N-1 or N-2'. Since this PR updates the test matrix to include N-2, this comment is now outdated and should be updated or removed to reflect the new testing setup.

[QuncCccccc]

Removed the last half sentence.

[loic-sharma]

Should we remove the TODO comment entirely? Feel free to punt this to a follow-up PR if that makes things easier.

[QuncCccccc]

I'll leave it for now, since legacy analysis still isn't set up in this repo. To handle it in a follow-up, we can move N-1/N-2 in multi_version_tasks.yaml to a legacy analysis job like flutter/packages has (remove-dev-dependencies, then analyze --lib-only --skip-if-not-supporting-dart-version), pass --skip-if-not-supporting-dart-version for stable too, and then remove the TODOs in both .repo_tool_config.yaml and multi_version_tasks.yaml.

[QuncCccccc]

Adding override: no versioning needed: raising the minimum SDK when the test matrix changes is version-exempt per the version policy. The dart fix changes don't change any public API, so they don't need a release either.

[loic-sharma]

LGTM. I'm not very familiar with this process, but I checked that this mirrors the docs.