fix(ci): brace-delimit version var in release-notes step - #105
Merged
Conversation
pwsh parses "$v:" as a drive-qualified variable reference, so the release-only "Release notes from CHANGELOG" step died with ParserError: Variable reference is not valid. ':' was not followed by a valid variable name character. Never seen before v2.0.0 because only tag pushes run this step; the nightly channel skips it. All build/test jobs of run 30425883196 were green - only publish failed, before creating the release. Co-Authored-By: Claude Fable 5 <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
1 participant
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.
The release-only "Release notes from CHANGELOG" step dies with a pwsh ParserError:
"$v:"parses as a drive-qualified variable. Brace-delimit it (${v}:).First hit by the v2.0.0 tag (run 30425883196): all build/test jobs green, publish failed before creating the release. Nightlies never run this step.
After merge: move the v2.0.0 tag to the new main tip and re-push so the release run uses the fixed workflow (re-running the old run would reuse the broken workflow snapshot from the tag).
🤖 Generated with Claude Code