Skip to content

fix(sources): use shared yamlEscape in blog release frontmatter#38

Merged
harlan-zw merged 1 commit intomainfrom
fix/blog-release-frontmatter-yaml-escaping
Mar 19, 2026
Merged

fix(sources): use shared yamlEscape in blog release frontmatter#38
harlan-zw merged 1 commit intomainfrom
fix/blog-release-frontmatter-yaml-escaping

Conversation

@oritwoen
Copy link
Copy Markdown
Collaborator

Description

formatBlogRelease was doing its own YAML escaping for the title field (only double quotes), and emitting version and url completely raw. Blog post titles with backslashes or newlines corrupt the frontmatter, and URLs with # fragments could get truncated as YAML comments depending on whitespace.

Third instance of the same bug class, after buildFrontmatter (#34) and formatRelease (#37).

Linked Issues

Related to #34, #37

Additional context

One-file change, function is internal and not exported. Typecheck clean.

formatBlogRelease hand-rolled YAML escaping for the title field
and left version/url completely unescaped. Blog post titles with
backslashes, newlines, or colons would produce corrupt frontmatter.

Third instance of the same bug class (after buildFrontmatter #34
and formatRelease #37).
@oritwoen oritwoen self-assigned this Mar 19, 2026
@harlan-zw harlan-zw merged commit a97c45f into main Mar 19, 2026
2 checks passed
@oritwoen oritwoen deleted the fix/blog-release-frontmatter-yaml-escaping branch March 19, 2026 14:49
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.

2 participants