Skip to content

Fix auto-tag workflow YAML (multi-line tag message broke literal block scalar)#78

Merged
OptimNow merged 1 commit into
mainfrom
claude/fix-auto-tag-yaml
May 4, 2026
Merged

Fix auto-tag workflow YAML (multi-line tag message broke literal block scalar)#78
OptimNow merged 1 commit into
mainfrom
claude/fix-auto-tag-yaml

Conversation

@OptimNow
Copy link
Copy Markdown
Owner

@OptimNow OptimNow commented May 4, 2026

Summary

The auto-tag workflow added in PR #76 has been failing in 0s on every push to main since it landed. Root cause: the tag message inside git tag -a -m "..." spanned multiple lines, and the inner lines started at column 1 of the file. YAML's run: | literal block requires consistent indentation - lines at column 1 broke out of the block scalar and confused the YAML scanner. Result: GitHub couldn't parse the workflow file (the API even exposed the workflow name as the file path, a tell that name parsing failed) and every run failed immediately before any step could execute.

Fix: collapse the tag message to a single line. The user-facing release notes are auto-populated by release.yml's generate_release_notes: true from the commit history, so the tag annotation itself does not need to be elaborate.

Test plan

  • python3 -c "import yaml; yaml.safe_load(open('.github/workflows/auto-tag-on-plugin-bump.yml'))" parses cleanly
  • After this merges, the next plugin.json bump on main should trigger the workflow successfully and create the matching tag automatically. (Today's v1.20.0 was created manually because of the YAML bug; v1.20.1 onward should be automatic.)

🤖 Generated with Claude Code

… line

The previous version had a multi-line tag message inside `git tag -a -m "..."`
where the inner lines started at column 1 of the file. YAML's `run: |` literal
block requires consistent indentation - lines at column 1 broke out of the
block scalar and confused the YAML scanner. Result: every run since PR #76
failed in 0s before any step could execute, with the API exposing the
workflow file path as the workflow `name` (a tell that name parsing failed).

Fix: collapse the tag message to a single line. The user-facing release notes
are auto-populated by release.yml's `generate_release_notes: true` from the
commit history between this tag and the previous one, so the tag annotation
itself does not need to be elaborate.

Validated locally with python yaml.safe_load - parses cleanly. The next
push to main that touches plugin.json will fire the workflow and create the
matching tag automatically.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@OptimNow OptimNow merged commit 453dc09 into main May 4, 2026
1 check passed
@OptimNow OptimNow deleted the claude/fix-auto-tag-yaml branch May 4, 2026 13:02
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