ci(release-actions): dispatch workflow to tag action versions + move v0#26
Merged
Merged
Conversation
Cutting an action version (the vX.Y.Z / moving v0 tags that consumers reference as actions/<name>@v0) was a manual local git-tag chore. This adds a workflow_dispatch that creates the immutable vX.Y.Z tag at the dispatched commit and force-advances the moving major tag (v0) to it — so @v0 consumers pick up the release with no edits. Separate from release-cli (the prebuilt binary). 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. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
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
Add a
release-actionsworkflow_dispatchthat cuts an action version of this repo: it creates the immutablevX.Y.Ztag at the dispatched commit and force-advances the moving major tag (v0) to it.Why
Consumers reference the composite actions as
vymalo/flutter-tools/actions/<name>@v0. Until now, releasing a new action version (and movingv0) was a manual localgit tagchore — the same friction we removed for the binary withrelease-cli. This makes it a button.Once
v0advances to amainthat includes the prebuilt-binary work, every@v0consumer (e.g. vymalo-shop) picks up the binary-based actions automatically — no edit on their side.How
workflow_dispatchwithversion(e.g.0.6.0, leadingvtolerated) andmove_major(default true).X.Y.Z, refuses to clobber an existingvX.Y.Z, creates the annotated tag, then force-movesv<major>.v0.1.0…v0.5.5were cut. Separate fromrelease-cli(which publishes thecli-v*binary the actions download).Note
v0is the moving tag many repos pin. Advancing it is intentional and instantly reversible (re-dispatch an older commit, or repointv0).🤖 Generated with Claude Code