git@github.com:flutter/engine.git/compare/0e90cb40822b...c43739ba53ce git log 0e90cb40822b..c43739ba53ce --no-merges --oneline 2019-08-20 skia-flutter-autoroll@skia.org Roll src/third_party/skia b081bc4a3139..aa3820a9123c (16 commits) (flutter/engine#11314) 2019-08-20 stuartmorgan@google.com Set FlutterMacOS podspec min version to 10.11 (flutter/engine#11306) 2019-08-20 iska.kaushik@gmail.com Do not Prepare raster cache if view_embedder is present (flutter/engine#11300) 2019-08-20 bkonyi@google.com Roll src/third_party/dart f7902889b6..027071318f (18 commits) 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.