Files
flutter/bin/internal
engine-flutter-autoroll 70c35bb551 Roll Flutter Engine from 590349006d23 to 8bacc3b38707 (5 revisions) (#134089)
590349006d...8bacc3b387

2023-09-06 jonahwilliams@google.com [Impeller] construct text frames on UI thread. (flutter/engine#45418)
2023-09-06 jiahaog@users.noreply.github.com Add import for `<unordered_map>` to fix the g3 build (flutter/engine#45471)
2023-09-06 skia-flutter-autoroll@skia.org Roll Skia from af473004622f to 0a253625a76a (2 revisions) (flutter/engine#45470)
2023-09-05 skia-flutter-autoroll@skia.org Roll Skia from 1019c10a2d38 to af473004622f (2 revisions) (flutter/engine#45469)
2023-09-05 zanderso@users.noreply.github.com Adds a comment on clang_arm64_apilevel26 toolchain usage (flutter/engine#45467)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry@google.com,zra@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
2023-09-06 02:17:03 +00:00
..

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.

The bin/internal/flutter_packages.version file specifies the version of the flutter/packages repository to be used for testing. The flutter/packages 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.