Skip to content

Release workflow: add manual workflow_dispatch trigger#35

Merged
cloudmanic merged 1 commit into
mainfrom
release-manual-dispatch
May 1, 2026
Merged

Release workflow: add manual workflow_dispatch trigger#35
cloudmanic merged 1 commit into
mainfrom
release-manual-dispatch

Conversation

@cloudmanic

Copy link
Copy Markdown
Owner

Why

Yesterday's PR #34 merged but no workflows ran, because the squash-merge commit message contained the literal string skip-CI (in my own PR description, ironically — I was describing the skip-CI bug). GitHub treats that string anywhere in the commit message as a global skip, so Release, Test, and Pages all silently no-op'd.

There's no escape hatch today: if release.yml's auto-trigger doesn't fire, the only way to recover is to push an empty commit to main. Adding workflow_dispatch lets the workflow be re-run on demand.

Test plan

  • Merge this PR
  • Open Actions → Release → Run workflow → main, and confirm it bumps the version, tags, runs goreleaser, and dispatches Pages
  • Confirm spice-edit.com picks up the new version

The release workflow only runs on push to main, so when something
suppresses the auto-trigger (a merge-commit message accidentally
carrying a skip-CI marker, a paused queue, etc.) we currently have
no recovery path short of pushing an empty commit. Adding
workflow_dispatch lets us rerun the release flow on demand against
the current main.
@cloudmanic cloudmanic merged commit b293f16 into main May 1, 2026
2 checks passed
@cloudmanic cloudmanic deleted the release-manual-dispatch branch May 1, 2026 07:52
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