
e52287a1b5...83239e141b
git log e52287a1b5572c73b19d085ccbe404f0aeddb5f6..83239e141b090aabe0e95fe8be8057c5710be89e --no-merges --oneline
83239e141 Roll src/third_party/skia 76616a10a786..c519fed6ddce (3 commits) (flutter/engine#7366)
62b9594d2 Roll src/third_party/skia 4683942a45f6..76616a10a786 (8 commits) (flutter/engine#7365)
23d087420 Roll Dart to version ec86471ccc47a62df8b4009e1fb37c66ff9dc91b (flutter/engine#7363)
78f6eb5c8 Roll src/third_party/skia 3b7e65107f67..4683942a45f6 (10 commits) (flutter/engine#7362)
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@chromium.org), 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.