tree: 463086ae0b5d67480b6efa8d176785177ee98a9f [path history] [tgz]
  1. canvaskit.version
  2. engine.merge_method
  3. engine.version
  4. flutter_plugins.version
  5. fuchsia-linux.version
  6. fuchsia-mac.version
  7. gradle_wrapper.version
  8. ios-deploy.version
  9. libimobiledevice.version
  10. libplist.version
  11. libzip.version
  12. material_fonts.version
  13. openssl.version
  14. README.md
  15. shared.bat
  16. shared.sh
  17. update_dart_sdk.ps1
  18. update_dart_sdk.sh
  19. usbmuxd.version
bin/internal/README.md

Flutter SDK dependency versions

The files in this directory specifies pinned versions of various dependencies of the flutter SDK.

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.

Ths bin/internal/flutter_plugins.version file specifies the version of the flutter/plugins repository to be used for testing. The flutter/plugins repository isn't an upstream dependency of flutter/flutter; it is only used as part of the test suite for verification, and the pinned version here makes sure that tests are deterministic at each flutter/flutter commit.