ci: add workflow_dispatch for manual re-runs#102
Merged
Conversation
Allows triggering the release workflow directly from main (which has the OIDC fix) without needing a release event. Useful when a release tag predates a workflow change and the tag cannot be moved.
schnz
approved these changes
Jun 16, 2026
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
2 participants
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.
Extends #101: adds
workflow_dispatchtrigger so the release can be manually re-run frommain(which has the OIDC fix), bypassing the tag-commit limitation.Background: GitHub uses the workflow from the tag's commit for
releaseevents. When a tag predates a workflow change, the old workflow runs.workflow_dispatchalways uses the workflow from the selected ref (default:main).The
taginput defaults tolatestand is ignored onreleaseevents (those useprereleaseflag as before).