feat(actions): codegen/android-setup/ios-setup use the prebuilt binary too - #27
Conversation
…y too The last three actions still ran the CLI via dart pub get + dart run (left that way because they set up Flutter anyway). Switch them to download the prebuilt binary like the other nine, so NO action resolves the CLI at runtime. They still set up Flutter — the binary shells out to dart/flutter/build_runner for the actual codegen. Saves the small per-run CLI pub-get and makes the fleet uniform. Also add docs/RELEASING.md (developer guide: the CLI-binary vs action-version artifacts, when to run release-cli vs release-actions, ordering, verify, rollback) and update the README accordingly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request migrates the android-setup, codegen, and ios-setup GitHub Actions to use the prebuilt flutter-tools CLI binary via the install-cli.sh script, eliminating the need to run dart pub get and dart run during execution. Additionally, the README has been updated, and a comprehensive release guide has been added in docs/RELEASING.md to document the release process for both the CLI binary and action tags. I have no feedback to provide as there are no review comments.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
1 participant
What
Migrate the last three actions still on
dart pub get+dart run—codegen,android-setup,ios-setup— to download the prebuilt binary viainstall-cli.sh, like the other nine. After this, no action invokesdartdirectly.They still set up Flutter; the binary just shells out to
dart/flutter/build_runnerfor the actual codegen. The install step is gated on the samerun-codegencondition in the two setup actions.Why
Small per-run saving (the CLI's own pub-get, ~2s) plus a uniform fleet — and it removes the last reason these actions needed the Dart SDK for the CLI itself, opening the door to future simplification.
Also
release-cli, action tags viarelease-actions), the decision matrix for what to run, the load-bearing ordering (binary before movingv0), verification, and rollback.Release note
Action-YAML + docs only — no
cli-version.txtbump and norelease-clineeded (Flow B in the guide). After merge: dispatchrelease-actionsto cut the next action version and movev0.🤖 Generated with Claude Code