docs(readme): document prebuilt CLI binary + dispatch release flow#25
Conversation
The top-level README still implied every action needs a Dart toolchain on PATH and documented no release process. Reflect the current architecture: - New 'Prebuilt CLI, not resolved at runtime' bullet (download a checksum-verified binary per OS/arch; codegen/*-setup keep dart run). - Reword the self-hosted bullet: only build/codegen actions read the toolchain from PATH; the rest run the prebuilt binary and need nothing. - New 'Releasing the CLI' section: bump cli-version.txt, then dispatch the release-cli workflow (no local git tag). 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 updates the README documentation to describe the transition to a prebuilt, checksum-verified CLI binary instead of resolving it at runtime, and adds instructions for releasing the CLI via a GitHub Actions workflow. The review feedback points out a minor inconsistency in the documentation regarding which actions require the Flutter toolchain on PATH versus those that run the prebuilt binary, and suggests a clearer phrasing.
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.
| GitHub-hosted or self-hosted runners. The build/codegen actions read your | ||
| Flutter toolchain from PATH (with opt-in setup steps); the rest just run the | ||
| prebuilt CLI binary and need nothing on PATH. |
There was a problem hiding this comment.
There is a slight inconsistency here. According to the new bullet point added in this PR, android-setup and ios-setup still use dart run (and thus require the Dart/Flutter SDK). However, this sentence states that "the rest [excluding build/codegen] just run the prebuilt CLI binary and need nothing on PATH", which incorrectly groups the setup actions into the category of actions that run the prebuilt binary and need nothing on PATH.
We should clarify this by distinguishing between build/codegen actions, setup actions, and the remaining utility/publishing actions.
| GitHub-hosted or self-hosted runners. The build/codegen actions read your | |
| Flutter toolchain from PATH (with opt-in setup steps); the rest just run the | |
| prebuilt CLI binary and need nothing on PATH. | |
| GitHub-hosted or self-hosted runners. The build/codegen actions read your | |
| Flutter toolchain from PATH (with opt-in setup steps), while setup actions | |
| configure it. The remaining publishing/utility actions run the prebuilt CLI | |
| binary and need nothing on PATH. |
1 participant
What
Update the top-level README to match the current architecture (the per-action READMEs were already reframed in #23).
dart pub getper run.codegen/android-setup/ios-setupkeepdart run(they set up Flutter anyway).cli-version.txt, then dispatch therelease-cliworkflow from the Actions tab — no localgit tag.Why
The README still implied every action needs a toolchain on PATH and documented no release process, both stale after the prebuilt-binary + workflow_dispatch changes (#23, #24).
🤖 Generated with Claude Code