a5a5595c95
064910eb3b...2ab34e4da1
git log 064910eb3ba266b2da35a794428f1f14d9b735a4..2ab34e4da16a3492946f81b76a4950c2c42ec358 --no-merges --oneline
2ab34e4da Roll src/third_party/skia 80f10d2c226a..30e918d9151d (9 commits) (flutter/engine#9174)
2fcd4e799 Do nothing if the params didn't change when compositing iOS platform views. (flutter/engine#8999)
9dfa276f2 Roll src/third_party/dart 224f82c21c..8cbb11cc55 (15 commits) (flutter/engine#9171)
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 (cbracken@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.