219bf59387...8b74cba20b
git log 219bf5938752e0030b491565af1910c137b83dd8..8b74cba20bb878d1e75747200f75dfaff5925bda --no-merges --oneline
8b74cba20 Make sure FlutterViewController flushs all pending touches when no longer active (flutter/engine#8400)
06cab8171 Roll src/third_party/skia e4628b10722f..51874e3e3712 (2 commits) (flutter/engine#8445)
5460926c0 Roll src/third_party/dart 9814cb1b9c..896f1c4bb9 (4 commits)
694fc5677 Build windows engine on GCE (flutter/engine#8442)
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 (chinmaygarde@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.