ci: disable Flutter SDK cache for floating 3.x version#1389
Merged
Conversation
spydon
force-pushed
the
fix/flutter-3x-windows-cache
branch
from
b35037d to
17705c9
Compare
The cached SDK contains runner-image-specific binaries that break silently when the Windows runner image is updated, causing Setup Flutter to fail with no error output. 3.19.x is unaffected because its cache is stable; only the floating 3.x (latest stable) is problematic.
spydon
force-pushed
the
fix/flutter-3x-windows-cache
branch
from
17705c9 to
6f7f3a5
Compare
mandarini
approved these changes
Jun 9, 2026
spydon
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
supabase_flutterCI was failing on "Test Flutter v3.x on windows-latest" at the Setup Flutter step with no visible error output.cache: truerestores a pre-compiled Flutter SDK (~1.8 GB) containing runner-image-specific binaries. When the runner image is updated, the cached binaries fail silently after extraction. The same issue can affect macOS and Linux runners.3.19.xis unaffected because it resolves to a pinned version whose cache remains stable across runner updates. Only the floating3.x(latest stable) is flaky.3.xcombinations viacache: ${{ matrix.flutter-version != '3.x' }}.Test plan
3.19.xmatrix combinations still use the cache as before