Repository navigation
v1.2.1 — hotfix: runtime-daily.yml failed GitHub's parser; every trigger was dead
Patch release, minutes after v1.2.0: the first workflow_dispatch of runtime-daily.yml was refused with HTTP 422 — "An expression was expected" (line 578) — which means the file failed GitHub's workflow parser and every trigger, including the daily cron, was dead on arrival in v1.2.0.
Root cause
Five comments carried a literal empty workflow expression — prose about expressions, written inside comments warning about expressions. GitHub scans run: block values for expressions even inside comments, and an empty one is a parse error. Nothing offline could catch it: PyYAML parses the file fine, and workflow-refs checks paths, not expressions.
Fixed
- The five comments now say "a workflow expression" instead of the token
Added
tests/test_workflow_expressions.py— tripwire asserting no workflow contains an empty expression (with a non-empty-workflow-list guard so it cannot be silently disarmed)
Verification
pytest1607 passed · validate / runtime_eval / synthesise all green ·do-harness verify --strictgreenworkflow_dispatchofruntime-daily.ymlnow accepted
🤖 Generated with Codebuff
Co-Authored-By: Codebuff noreply@codebuff.com