a3f0704f25
Towards https://github.com/flutter/flutter/issues/162201. **NOTE**: This renames the environment variable to `FLUTTER_PREBUILT_ENGINE_VERSION`. --- We occasionally break ourselves, our users, and the Dart up (or is it down? side-ways) stream repos (i.e. HHH) when we change how the undocumented [`update_engine_version.sh`](https://github.com/flutter/flutter/blob/master/bin/internal/update_engine_version.sh) script, and it's Windows counterpart [`update_engine_version.ps1`](https://github.com/flutter/flutter/blob/master/bin/internal/update_engine_version.ps1) work, but have no way of knowing until N days/weeks later when someone tells us. For example, <https://flutter-review.googlesource.com/c/recipes/+/62400>. This is my attempt to encode "this is what you can guarantee by calling this script". It _still_ will be an internal only API that we might rev at any time, but at least we: 1. Can tell the Dart team "this is tested and how it works" 2. If we want to change it, the tests will keep us from changing it without informing folks it changed These tests should (in theory) cover both Linux/MacOS and Windows. /cc @a-siva
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 where to find compiled artifacts
of the engine. These artifacts are compiled in the Merge Queue for every commit
in the flutter repository.
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.