Skip to content

ci: pin Flutter 3.47.1 so Linux releases ship the 120 Hz engine - #1246

Merged
ZhuchkaTriplesix merged 1 commit into
devfrom
ci/flutter-3.47.1
Oct 9, 2026
Merged

ZhuchkaTriplesix merged 1 commit into
devfrom
ci/flutter-3.47.1

Conversation

@ZhuchkaTriplesix

Copy link
Copy Markdown
Member

Refs #980

Problem

scripts/linux/apply_patched_engine.sh downloads the vsync-patched libflutter_linux_gtk.so from QueryaHub/flutter-engine-linux-120hz by the engine content hash. The only published build, engine-11d79658c444477b06513d32b52c8c4ccb7276b0, is for Flutter 3.47.1. CI and release pinned 3.41.6, whose content hash is 5cdd32777948fa7a648fac915f8da7120ac7e97a.

The 0.4.18 release log shows the result:

apply_patched_engine.sh: no patched engine published for content hash 5cdd3277… — shipping stock Linux engine (capped at 60 fps)

Change

  • flutter-version: '3.47.1' in ci.yml (3 jobs), release.yml (4 jobs) and benchmark.yml.
  • docs/motion-and-high-refresh.md: toolchain line updated.

Not changed

.devcontainer/Dockerfile (and its line in docs/ci-runners.md) stays on 3.41.6: ghcr.io/cirruslabs/flutter has no 3.47.1 image yet (newest tag 3.44.0).

How to check

  • This PR's CI runs analyze and tests on 3.47.1.
  • The engine splice runs only on tags. On the next release, the Linux build log should show spliced in vsync-patched engine for content hash 11d79658… instead of the warning.

apply_patched_engine.sh looks up a patched libflutter_linux_gtk.so by the
engine content hash. The only published build (engine-11d79658...) is for
Flutter 3.47.1, while CI and release pinned 3.41.6 (content hash 5cdd3277...).
Release 0.4.18 therefore shipped the stock engine, capped at 60 fps.

The dev container stays on 3.41.6: cirruslabs/flutter has no 3.47.1 image.
@ZhuchkaTriplesix
ZhuchkaTriplesix merged commit 5d6d609 into dev Oct 9, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant