ef2bed65db...39a950e5d1
git log ef2bed65db22b1ce3d05947d5cfa3927eb6fa975..39a950e5d1d1cbeb3d70334c6275d224e843b30e --no-merges --oneline
39a950e5d remove legacy build deps (flutter/engine#8820)
c0be4e277 Fix api conformance check (flutter/engine#8817)
30639ee7b Allow FlutterEngine to be used on back-to-back screens (#31264). (flutter/engine#8808)
45d0c4d11 Roll src/third_party/skia cd5d14619fe2..68eb8c276355 (4 commits) (flutter/engine#8815)
9856479ec Roll src/third_party/dart b6997deb3e..1577b95c93 (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 (amirha@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.