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.

Wait actually is that the right commit? Do bin/internal changes count as engine changes?

Wait actually is that the right commit? Do bin/internal changes count as engine changes?

Looks like the issue is that the release builder failed to actually build this commit: https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Linux%20flutter_release_builder/1030/overview

The previous commit failed because we hadn't made a recipes branch for this version apparently. I manually created the recipes branch and kicked off a new release builder: https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Linux%20flutter_release_builder/1031/overview

That appears to be working so far. After it completes I can retry the presubmits.

Wait actually is that the right commit? Do bin/internal changes count as engine changes?

To answer this, bin/internal/release-candidate-branch.version is specifically included as part of the content aware hash and whether to build the engine.