fix(ci): remove literal ${{ }} from release.yml comment (422 on dispatch)#49
Merged
Conversation
Release v0.6.1 — prompt tightening (caveman measured & dropped)
PR #46's comment wrote a literal empty GitHub expression `${{ }}` inside the "Create tag and GitHub release" run block. GitHub scans the entire run script (comments included) for template expressions, so the empty one fails to parse — `workflow_dispatch` returned HTTP 422 "An expression was expected" (Line 61). Rephrase the comment to describe the env-var pattern without writing a literal expression, and add a note so it isn't reintroduced. No behavior change to the release step. (v0.6.1 was tagged via a direct tag push, which worked in this environment; this restores the server-side dispatch fallback for when it 403s.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #46 left a literal empty GitHub expression
\${{ }}inside the release.yml "Create tag and GitHub release" run block (in a comment). GitHub scans the whole run script for template expressions, so the empty one fails to parse —workflow_dispatchreturns HTTP 422 "An expression was expected", breaking the server-side release fallback.Surfaced while releasing v0.6.1: the dispatch 422'd, so v0.6.1 was tagged via a direct tag push (which worked in this environment). This restores the dispatch fallback for environments where tag pushes 403.
Fix: rephrase the comment to describe the env-var pattern without writing a literal expression, plus a note so it isn't reintroduced. No behavior change to the release step. YAML validated; no remaining literal
\${{ }}in run scripts.🤖 Generated with Claude Code