fix(release): add workflow_dispatch to retrigger for existing tags#167
Merged
zeitlinger merged 3 commits intomainfrom Apr 13, 2026
Merged
fix(release): add workflow_dispatch to retrigger for existing tags#167zeitlinger merged 3 commits intomainfrom
zeitlinger merged 3 commits intomainfrom
Conversation
Allows manually triggering the release workflow for a specific tag, useful when the automatic push trigger fails. Passes the tag as ref to both checkout and upload-rust-binary-action via GITHUB_REF override. Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
GITHUB_REF cannot be overridden via env: — the runner sets it before steps execute. The action's ref input is the correct way to pass an arbitrary tag ref for workflow_dispatch triggers. Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a manual “escape hatch” to the release workflow so maintainers can re-run releases for an existing tag when the normal tag-push trigger can’t be used (e.g., due to tag protection / immutable release policies).
Changes:
- Add
workflow_dispatchtrigger with a requiredtaginput. - Use the provided tag to select the
refforactions/checkoutand for the Rust binary upload step (via the action’srefoverride). - Preserve the existing
push-on-tag (v*) trigger path.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Use github.event_name guard instead of inputs.tag truthiness check — safer on push events where inputs context is unavailable - Clarify tag input description to prevent refs/tags/ prefix (which would double-prefix the constructed ref) Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
martincostello
approved these changes
Apr 13, 2026
This was referenced Apr 13, 2026
Merged
zeitlinger
added a commit
that referenced
this pull request
Apr 16, 2026
### Added - *(release)* migrate from release-please to release-plz ([#171](#171)) ### Fixed - *(release)* use correct template variable in pr_body ([#178](#178)) - *(release)* suppress component prefix in release-please tags ([#166](#166)) - *(release)* add workflow_dispatch to retrigger for existing tags ([#167](#167)) ### Other - move icon to assets/ to fix release-plz ([#177](#177)) - *(deps)* update dependency npm:renovate to v43.102.11 [security] ([#174](#174)) - *(deps)* update rust crate similar to v3.1.0 ([#173](#173)) - *(deps)* update dependency github:mvdan/sh to v3.13.1 ([#163](#163)) > [!IMPORTANT] > Close and reopen this PR to trigger CI checks. --------- Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
This was referenced Apr 16, 2026
Closed
Closed
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.
Summary
workflow_dispatchtrigger with ataginput to the release workflowrefto bothactions/checkoutandupload-rust-binary-action(viaGITHUB_REFoverride)Why
The
v0.20.0release workflow failed because the tag wasflint-v0.20.0(release-please bug, fixed in #166) and the release had to be created manually. Due to tag protection rules and the immutable-releases policy, there was no way to retrigger the workflow. This adds an escape hatch for that situation.