tree: c3c5ea80508e992eee881c59aba5fbc631e6c403 [path history] [tgz]
  1. engine.merge_method
  2. engine.version
  3. fuchsia-linux.version
  4. fuchsia-mac.version
  5. gradle_wrapper.version
  6. ios-deploy.version
  7. libimobiledevice.version
  8. libplist.version
  9. libzip.version
  10. material_fonts.version
  11. openssl.version
  12. README.md
  13. shared.bat
  14. shared.sh
  15. update_dart_sdk.ps1
  16. update_dart_sdk.sh
  17. usbmuxd.version
bin/internal/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.