Skip to content

ci: fix invalid YAML in the VS Code extension release workflow - #252

Merged
zackees merged 1 commit into
mainfrom
fix/vscode-release-workflow-yaml
Sep 15, 2026
Merged

zackees merged 1 commit into
mainfrom
fix/vscode-release-workflow-yaml

Conversation

@zackees

@zackees zackees commented Sep 15, 2026

Copy link
Copy Markdown
Member

Summary

.github/workflows/vscode-extension-release.yml used flow mappings such as env: { GH_TOKEN: ${{ github.token }} }. That is invalid YAML because the expression braces end the mapping. GitHub rejected the file, so every push to every branch, including main, showed a failed vscode-extension-release.yml run, even though the workflow only triggers on vscode-v* tags.

Both env maps now use block style.

Validation

  • Every workflow file under .github/workflows parses with PyYAML.
  • actionlint passes on the changed workflow.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VfXV1EpgAvMZzXJfbGZPRG

`env: { GH_TOKEN: ${{ github.token }} }` is not valid YAML: the `${{`
expression's braces terminate the flow mapping. GitHub rejected the whole
file and reported a failed "vscode-extension-release.yml" run on every
push to every branch, including main, although the workflow only runs on
`vscode-v*` tags. Both env maps now use block style; every workflow file
parses and actionlint passes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VfXV1EpgAvMZzXJfbGZPRG
@zackees
zackees merged commit 83ae037 into main Sep 15, 2026
@zackees
zackees deleted the fix/vscode-release-workflow-yaml branch September 15, 2026 22:41
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