release: add workflow_dispatch trigger for on-demand (draft) builds#2
Closed
mariotaku wants to merge 1 commit into
Closed
release: add workflow_dispatch trigger for on-demand (draft) builds#2mariotaku wants to merge 1 commit into
mariotaku wants to merge 1 commit into
Conversation
The release pipeline only ran on `release: published`, so cutting a release required manually creating it in the GitHub UI first. Add a workflow_dispatch trigger that takes a tag input and (by default) creates a draft release with the built .deb artifacts attached, for review before publishing. The existing published-release behaviour is unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011jY7WzoWeU9TWRBhWJ2Wbq
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
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.
Why
The release pipeline only triggered on
release: published, so cutting a release required manually creating the GitHub Release in the UI first. There's no way to build the.debartifacts on demand (e.g. to validate a release, or to produce a draft for review).What
Add a
workflow_dispatchtrigger torelease.yml:taginput (required) — the tag to create the release on, e.g.v20260626-cd038b0.draftinput (defaulttrue) — create the release as a draft for review before publishing.The
ncipollo/release-actionstep now falls back to the dispatch inputs:The existing
release: publishedbehaviour is unchanged (for that eventinputs.tagis empty anddraftevaluates tofalse).Use
Once merged, a release can be cut on demand (Actions → Release → Run workflow, or via API) — it builds all four toolbox debs and attaches them to a draft release at the given tag, ready to review and publish.
This is the mechanism to ship the global-scope symbol-resolution fix (#1) as
v20260626-cd038b0.🤖 Generated with Claude Code
Generated by Claude Code