fix: Default force_bump to false for scheduled release runs

[yelizhenden-mdb]

Summary

Scheduled Release Runner runs have been failing since 2026-09-22 (after #1493): the four Release OpenAPI Spec for <env> jobs never start, and only the deprecated V1 release runs. The failure is silent — no job ever fails, so the retry/failure handlers never create a GH issue or Jira ticket.

Root cause

force_bump is a workflow_dispatch boolean input. Scheduled workflows send it as null and it resolves to an empty string, so the runner passed force_bump: '' to release-spec.yml, which declares the input as type: boolean. GitHub rejects '' while evaluating the reusable-workflow inputs:

load job template context: load reusable workflow context: evaluate reusable workflow inputs:
.github/workflows/release-spec-runner.yml (Line: 69, Col: 19): Unexpected value ''

This happens while GitHub builds the job graph, before any of the four jobs are created, so:

• the env jobs never appear in the run — only release-spec-v1-prod starts (it doesn't take force_bump), which made it look like "only the deprecated workflow runs";
• the runner-level retry-handler/failure-handler only watch release-preparation (which succeeds), so nothing is reported — no failed job, no issue, no Jira ticket. The only trace is the error annotation on the run page.

Evidence: every scheduled run fails since the first schedule after #1493 merged (2026-09-22T12:15Z), while every manual workflow_dispatch succeeds — the dispatch UI supplies a real boolean, so validation passes.

Fix

Coerce to a real boolean at the four call sites in release-spec-runner.yml:

force_bump: ${{ inputs.force_bump || false }}

• schedule: empty/null input → false (valid boolean, validation passes)
• workflow_dispatch: the real boolean from the UI passes through unchanged, so the force-bump feature keeps working

Testing

• After merging, verify the next scheduled run (every 2h, Mon–Fri) creates the DEV/QA/STAGING/PROD release jobs

[lovisaberggren]

Ty!