chore: cache the flutter sdk and gradle deps in android builds - #3225
Merged
Conversation
The android workflow was setting up flutter its own way with subosito/flutter-action plus hand-rolled cache restore/save steps, duplicating what .github/actions/setup-flutter already does. Beyond the duplication, the hand-rolled cache never actually hit. Its keys were only ever written by this workflow, which runs on tags, and a tag push gets its own cache scope - so every release missed on restore and saved to a scope no later run could read. setup-flutter's keys are already warmed into master's scope by pr-check, so a release now picks them up. Also drops the second way of installing flutter from the repo. If fvm is going away it should go away everywhere at once, not one workflow at a time. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ks57GnHLcu8SQsUpGWKm8y
zlshames
force-pushed
the
claude/android-build-github-action-1jh5i8
branch
from
August 15, 2026 11:12
c2acb55 to
1564596
Compare
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
3 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.
Matches what the desktop workflows already do, so a tag build isn't refetching the whole SDK every time. Uses an explicit cache-path with split restore/save rather than the setup action's own cache input, which delegates to a floating actions/cache@v3.