Skip to content

fix: pass a boolean to the reusable workflow's force input — releases dead since May - #49

Merged
ronaldtse merged 1 commit into
mainfrom
fix/release-boolean-input
Oct 10, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
fix/release-boolean-input

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Problem

Releases from this repository have been silently dead since the CI simplification: the Release workflow fails at trigger time with zero jobs started ("This run likely failed because of a workflow file issue"). The May-13 release is still the latest.

Root cause

force: ${{ github.event.inputs.force || 'false' }}

On push events this expression evaluates to the string 'false', but the reusable workflow (actions-mn/.github, metanorma-release.yml) declares force as type: boolean. GitHub validates workflow_call inputs before starting anything — a string for a boolean input aborts the run.

Fix

force: ${{ github.event.inputs.force == 'true' }}

A real boolean on both triggers: push → null == 'true' → false; workflow_dispatch → 'true' == 'true'.

Merging this also republishes all 134 administrative documents with their new abstracts (PR #48).

github.event.inputs.force || 'false' evaluates to the STRING 'false'
on push events; the reusable workflow declares force as type: boolean,
so GitHub rejects the call before any job starts (the release has been
silently dead since the CI simplification). == 'true' yields a real
boolean on both push (null == 'true' -> false) and dispatch.
@ronaldtse
ronaldtse merged commit 8029ff0 into main Oct 10, 2026
1 check passed
@ronaldtse
ronaldtse deleted the fix/release-boolean-input branch October 10, 2026 01:17
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