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.

@godofredoc Thanks for creating this cherry-pick request. I'm interested in learning how the cherry-pick process works and I read the wiki article. But for me it's unclear how to pick the right branch. Just out of curiosity: Why have you picked flutter-3.13-candidate.0 as target branch and not one of the other 19 branches?

et branch and not one of the other 19 branches?

Several release candidate branches are created per week to go through additional testing. Once we are ready for a new release, one of the release candidate branches is selected based on alignment with dart-sdk and some test greeness criteria.

During the release process the candidate branch is promoted to stable or beta and the source release candidate branch is updated here: https://github.com/flutter/flutter/blob/stable/bin/internal/release-candidate-branch.version.

Hotfixes are applied as cherry-picks to the release candidate branch and then the release candidate branch is pushed to stable or beta.