ci(release-cli): release via workflow_dispatch instead of tag push - #24
Merged
Conversation
Cutting a release no longer needs a local `git tag` + push. The workflow now
runs from the Actions tab ("Run workflow"); it reads the version from
cli-version.txt, then creates the cli-v<version> tag + GitHub Release at the
dispatched commit (action-gh-release creates the tag if absent). Bump
cli-version.txt to release a new version.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
What
Switch the
release-cliworkflow from a tag-push trigger toworkflow_dispatch— releases are now cut from the GitHub Actions "Run workflow" button, no localgit tag+ push from a laptop.Why
Tagging from a developer machine is clunky and easy to get wrong (wrong ref, forgotten push, prefix typos). A dispatch button is reproducible, auditable, and runnable by anyone with Actions access.
How
workflow_dispatch(no inputs).releasejob reads the version fromcli-version.txt(still the single source of truth), thensoftprops/action-gh-releasecreates thecli-v<version>tag + Release at the dispatched commit if it doesn't already exist.cli-version.txt, merge it, then dispatch.The build matrix (linux-x64, linux-arm64, macos-15 arm64) is unchanged.
Notes
workflow_dispatchonly shows the "Run workflow" button once this file is on the default branch, so it becomes available after merge.🤖 Generated with Claude Code