Skip to content

[ci]: Trigger releases manually with version bump - #18

Merged
pseudomuto merged 1 commit into
masterfrom
ci/manual-release
Jul 20, 2026
Merged

[ci]: Trigger releases manually with version bump#18
pseudomuto merged 1 commit into
masterfrom
ci/manual-release

Conversation

@pseudomuto

Copy link
Copy Markdown
Owner

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.

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.
@pseudomuto
pseudomuto merged commit b14c29a into master Jul 20, 2026
3 checks passed
@pseudomuto
pseudomuto deleted the ci/manual-release branch July 20, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant