b296d95391
git@github.com:flutter/engine.git/compare/426ea8dba6ea...f8e7453f1106 git log 426ea8dba6ea..f8e7453f1106 --no-merges --oneline 2019-08-15 skia-flutter-autoroll@skia.org Roll fuchsia/sdk/core/linux-amd64 from pCY3J... to _fvZN... (flutter/engine#11020) 2019-08-15 skia-flutter-autoroll@skia.org Roll src/third_party/skia c061d31c2415..319fd3d7bcb4 (9 commits) (flutter/engine#11018) 2019-08-15 bkonyi@google.com Roll src/third_party/dart e35e8833ee..e35e8833ee (0 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 (stuartmorgan@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.