[ci]: Trigger releases manually with version bump - #18
Merged
Conversation
Releases previously required creating and pushing a signed tag from a
local machine via the tag/tag:{patch,minor,major} Taskfile tasks, which
then fired the tag-push release workflow.
Switch the release workflow to workflow_dispatch with a required bump
input (patch/minor/major). The job computes the next version from the
latest stable vX.Y.Z tag, creates and pushes an annotated tag, then runs
goreleaser. Everything happens in one job because a tag pushed with the
default GITHUB_TOKEN does not retrigger a tag-push workflow, so the old
two-step flow could not work from CI.
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.
Releases previously required creating and pushing a signed tag from a local machine via the tag/tag:{patch,minor,major} Taskfile tasks, which then fired the tag-push release workflow.
Switch the release workflow to workflow_dispatch with a required bump input (patch/minor/major). The job computes the next version from the latest stable vX.Y.Z tag, creates and pushes an annotated tag, then runs goreleaser. Everything happens in one job because a tag pushed with the default GITHUB_TOKEN does not retrigger a tag-push workflow, so the old two-step flow could not work from CI.