fix(ci): the runner executed "|" instead of every multi-line script — block scalars now parsed #5466
ccantynzAI Reviewcommented 24d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 24d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
The root cause of the all-red Actions history: the runner prefers
workflow-parser-ext, which had no block-scalar handling —run: |parsed to the literal string"|", and the base/ext merge spreads ext last, clobbering the base parser's correct multi-line script. Every multi-linerun:step on the platform executedbash -c '|'→ instant syntax error (~500ms). Confirmed via run #255's stderr:syntax error near unexpected token `|'.parseExtendednow reads|,|-,|+,>,>-,>+(dedented body, literal/folded joining, chomping). Verified against the real deploy.yml — the 14-line script parses intact.Stacked with #5465 (branch filters + verify-deploy rewrite): the next push to main should produce the first genuinely green run in this workflow's history.
tsc clean; workflow suites 206 run / 0 fail.
🤖 Generated with Claude Code