Repository navigation
ci: create release tags from manual workflow input - #3127
Merged
Merged
Conversation
Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>
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.
Switch releases from tag pushes to manual dispatch with a required
v-prefixed tag, such asv0.1.0. The workflow builds the selected branch's commit and creates the tag and GitHub release after all publishing jobs succeed.Existing tags are rejected before publishing, release runs are serialized, and the development guide includes the manual release command.
Validated with actionlint (excluding the existing Blacksmith runner-label warning) and 16 local validation cases covering tag inputs, existing tags, and release wiring. The publishing workflow was not run.