You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: start using the content aware hash for downloading artifacts (flutter#171927)
towards flutter#171790
Use the content aware hash when downloading engine artifacts. These are
currently produced when changes to DEPs, engine/, or the release file
are changed in a not-seen-before way.
We can eventually remove `engine.version` being tracked in release
branches as an optimization.
`FLUTTER_PREBUILT_ENGINE_VERSION` will stay for overriding the
engine.version for testing. Though Cocoon does not need to actually set
it for framework only PRs anymore.
Copy file name to clipboardExpand all lines: docs/tool/Engine-artifacts.md
+16-15Lines changed: 16 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,18 +13,19 @@ for Android, iOS, and so-on).
13
13
14
14
When using a _released_ version of Flutter, i.e. from a channel such as `stable`,
15
15
[`bin/internal/engine.version`](../../bin/internal/engine.version) is set to the
16
-
git commit SHA for a merged commit in `https://github.com/flutter/flutter`, where
16
+
content hash SHA for a merged commit in `https://github.com/flutter/flutter`, where
17
17
the engine artifacts have already been pre-built and uploaded.
18
18
19
19
When using the `master` channel, or _contributing_ to Flutter (which is typically
20
-
as a fork of Flutter's `master` channel), the git commit SHA is _computed_ by
21
-
using `git merge-base HEAD upstream/master` (falling back to `git merge-base HEAD origin/master`
22
-
to support direct forks or `flutter/flutter`).
20
+
as a fork of Flutter's `master` channel), the engine SHA is _computed_ by
21
+
generating a content-aware hash of files that affect the engine build (such as
22
+
`DEPS` and the `engine` directory itself).
23
23
24
24
For _advanced_ use-cases, such as on CI platforms, or for custom 1-off testing
25
25
using a pre-built Flutter engine (to use a _locally_ built Flutter engine see
26
26
[locally built engines](../contributing/testing/Running-and-writing-tests.md#locally-built-engines)), the environment variable `FLUTTER_PREBUILT_ENGINE_VERSION` can be set,
27
-
again to a git commit SHA for a merged commit in `flutter/flutter`:
27
+
again to a engine SHA for a merged commit in `flutter/flutter`. This is only needed
28
+
if different artifacts from the content sha are desired:
> As of [`b0ccfb53801abc9b0aa93e7cca3a3841513c3086`](https://flutter.googlesource.com/recipes/+/b0ccfb53801abc9b0aa93e7cca3a3841513c3086) (May 6 2025), the packaging release process will refuse to let you publish a
0 commit comments