fix(ci): use CUE raw multi-line strings in release generator#25228
Merged
fix(ci): use CUE raw multi-line strings in release generator#25228
Conversation
Contributor
|
Your preview site for the vector.dev will be ready in a few minutes, please allow time for it to build. Heres your preview link: |
pront
added
domain: releasing
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
pront
force-pushed
the
prepare-v-0-55-0-website
branch
from
f1d3efe to
a199445
Compare
github-actions
Bot
removed
the
domain: releasing
Fragment descriptions are embedded into CUE via `"""..."""`, where backslashes are still interpreted as escape sequences. A fragment containing e.g. a shell line continuation (`\<newline>`) produces invalid CUE and breaks `cue export`, which is then used by the next `cargo vdev release prepare` invocation. Switch to raw multi-line strings (`#"""..."""#`) so backslashes are literal and no escaping is needed on the description content. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
Your preview site for the vector.dev will be ready in a few minutes, please allow time for it to build. Heres your preview link: |
pront
force-pushed
the
prepare-v-0-55-0-website
branch
from
a199445 to
4746bdb
Compare
thomasqueirozb
approved these changes
Apr 20, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
scripts/generate-release-cue.rbembeds each changelog fragment's description into a CUE"""..."""multi-line string. Backslashes inside that string are still interpreted as escape sequences, so any fragment containing e.g. a shell line-continuation (\<newline>) produces anunknown escape sequenceerror incue export. That in turn makes the nextcargo vdev release preparerun fail, because the generator parses prior release cue files at startup.This PR switches the generated
descriptionblocks to CUE raw multi-line strings (#"""..."""#) so backslashes are literal and fragments can contain arbitrary shell snippets, regex examples, Windows paths, etc. without bespoke escaping.Vector configuration
N/A — release tooling only.
How did you test this PR?
masteragainstchangelog.d/graphql_to_grpc_api.breaking.md(which containsgrpcurl -plaintext \line continuations).website/cue/reference/releases/0.55.0.cue, and reranbundle exec ./scripts/generate-release-cue.rb --new-version 0.55.0 --no-interactive. The script completes without anyunknown escape sequence:output.cue exporton the regenerated0.55.0.cue. Previously this failed withunexpected token at ''(empty output from cue); now it returns valid JSON.descriptionfield.Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
N/A
🤖 Generated with Claude Code