🐛 fix(ci): version-bump fallback for workflow_dispatch trigger #31

arcodange · 2026-05-03T16:42:12+02:00

arcodange commented

2026-05-03 16:42:12 +02:00

Summary

Manually-triggered CI runs (workflow_dispatch) were failing on the version-bump step even when tests passed, because ${{ github.event.head_commit.message }} is empty for that event type. ci-version-bump.sh then exits 1 with "Error: Commit message not provided".

Fix

Fall back to git log -1 --pretty=%B when the event context provides no commit message. Push-event behavior unchanged.

Observed in

CI run #615 (manually triggered after PR #28 merge): build OK, BDD passed (49.7% coverage), but version-bump failed → entire workflow marked failure. Same pattern would have masked many other valid runs.

Test plan

Manually trigger workflow on main → should now succeed
Auto-triggered push → should still succeed (no change to that path)

## Summary Manually-triggered CI runs (`workflow_dispatch`) were failing on the version-bump step even when tests passed, because `${{ github.event.head_commit.message }}` is empty for that event type. `ci-version-bump.sh` then exits 1 with "Error: Commit message not provided". ## Fix Fall back to `git log -1 --pretty=%B` when the event context provides no commit message. Push-event behavior unchanged. ## Observed in CI run #615 (manually triggered after PR #28 merge): build OK, BDD passed (49.7% coverage), but version-bump failed → entire workflow marked failure. Same pattern would have masked many other valid runs. ## Test plan - [ ] Manually trigger workflow on main → should now succeed - [ ] Auto-triggered push → should still succeed (no change to that path)

arcodange added 1 commit 2026-05-03 16:42:13 +02:00

🐛 fix(ci): version-bump fallback for workflow_dispatch trigger 3e20362daf

The CI workflow_dispatch event provides no head_commit, so
${{ github.event.head_commit.message }} expands to empty.
ci-version-bump.sh requires a commit message and exits 1 if absent,
causing manually-triggered CI runs to fail in the version-bump step
even though the actual tests passed.

Fix: fall back to `git log -1 --pretty=%B` when the GitHub event
context provides no commit message. Maintains push-event behavior
unchanged (head_commit.message still primary source).

Observed in CI #615 (manual trigger after PR #28 merge): tests passed,
build OK, but version-bump failed → entire workflow marked FAILURE.

🤖 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>