firka/flutter
firka/flutter
4
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
flutter/bin/internal
History
engine-flutter-autoroll beaf776edb Roll engine 36acd02c9412..9b6d5031a3c0 (5 commits) (#27104) 
* 4f02f7e22 Roll src/third_party/skia aa6ca0a8bfc1..74b6cf3a7215 (2 commits) (flutter/engine#7583)

* fe2609f5c Roll src/third_party/skia 74b6cf3a7215..a7cb690dc8fe (1 commits) (flutter/engine#7584)

* 204a09910 Roll src/third_party/skia a7cb690dc8fe..9bc76d96f986 (1 commits) (flutter/engine#7585)

* 5cfc0249a Roll src/third_party/skia 9bc76d96f986..d41c1876d834 (6 commits) (flutter/engine#7586)

* 9b6d5031a Roll src/third_party/dart a5030ed92f..a5030ed92f (0 commits)
2019-01-26 11:23:17 -08:00
..
engine.merge_method
Switch engine.merge_method back to squash (#24319)
2018-11-13 17:12:36 -08:00
engine.version
Roll engine 36acd02c9412..9b6d5031a3c0 (5 commits) (#27104)
2019-01-26 11:23:17 -08:00
goldens.version
[Material] Theme data type for cards (#26796)
2019-01-24 11:01:21 -05:00
gradle_wrapper.version
Make artifacts URLs configurable. (#13380)
2017-12-07 16:30:23 +01:00
material_fonts.version
Make artifacts URLs configurable. (#13380)
2017-12-07 16:30:23 +01:00
README.md
Add engine merge method configuration (#23953)
2018-11-07 13:06:38 -08:00
update_dart_sdk.ps1
update_dart_sdk.ps1: Fall back to Invoke-WebRequest if BITS fails (#19873)
2018-07-27 14:29:20 -07:00
update_dart_sdk.sh
Update links for China help (#25238)
2018-12-21 10:12:49 -08:00

README.md

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.