Add manual dispatch trigger to the release workflow - #96
Draft
paven wants to merge 1 commit into
Draft
Conversation
paven
force-pushed
the
release-dispatch-support
branch
6 times, most recently
from
September 9, 2026 14:47
e77ee38 to
8955069
Compare
paven
force-pushed
the
release-dispatch-support
branch
from
September 9, 2026 14:51
8955069 to
06e4833
Compare
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.
Lets the Unified Release Orchestrator be triggered manually after a merge, so a release is still possible when a PR is merged without a
release:*label.How to use
After merging a PR without a label: Actions tab -> Unified Release Orchestrator -> Run workflow -> branch main, channel (default alpha). Or: