250b99bd27...d4d4883216
git log 250b99bd275ad7622f239a8042f6a6d31b5b95f1..d4d4883216fd1c1dfc17d41418a960c002cfff57 --no-merges --oneline
d4d488321 Roll src/third_party/skia 174a3f61fd5d..a695da930510 (2 commits) (flutter/engine#8242)
2d5376c09 Roll src/third_party/skia 2c4ceca62d27..174a3f61fd5d (1 commits) (flutter/engine#8239)
b05399901 Roll src/third_party/skia e409441aee0d..2c4ceca62d27 (1 commits) (flutter/engine#8238)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (liyuqian@google.com), and stop
the roller if necessary.
Dart SDK dependency
The bin/internal/engine.version file controls which version of the Flutter engine to use.
The file contains the commit hash of a commit in the https://github.com/flutter/engine repository.
That hash must have successfully been compiled on https://build.chromium.org/p/client.flutter/ and had its artifacts (the binaries that run on Android and iOS, the compiler, etc) successfully uploaded to Google Cloud Storage.
The /bin/internal/engine.merge_method file controls how we merge a pull
request created by the engine auto-roller. If it's squash, there's only one
commit for a pull request no matter how many engine commits there are inside
that pull request. If it's rebase, the number of commits in the framework is
equal to the number of engine commits in the pull request. The latter method
makes it easier to detect regressions but costs more test resources.