Skip to content

Wrap archival release notes in raw template tags - #20

Closed
jesseditson wants to merge 1 commit into
mainfrom
claude/liquid-parsing-code-blocks-t0kilb
Closed

jesseditson wants to merge 1 commit into
mainfrom
claude/liquid-parsing-code-blocks-t0kilb

Conversation

@jesseditson

Copy link
Copy Markdown
Collaborator

Summary

Added Liquid template {% raw %} and {% endraw %} tags around the body content of the Archival 0.22.0 release notes to prevent template syntax from being processed.

Changes

  • Wrapped the release notes body content with {% raw %} at the beginning and {% endraw %} at the end
  • This prevents Liquid template engine from interpreting the code examples and template syntax shown in the release notes (e.g., {{ posts.something.name }}, {{ sample_menus.lunch.url }})

Details

The release notes contain multiple examples of Archival's new object addressing syntax using Liquid template syntax. Without the raw tags, the template engine would attempt to process these examples, which could cause rendering issues or unexpected behavior. The raw tags ensure the examples are displayed as literal text.

https://claude.ai/code/session_01YXKzyT7wjxop7Me8egDDqZ

The release note's inline code samples contain liquid, which archival
renders rather than prints, and comrak's escaping turns the quotes in
`where: "slug", "lunch"` into `"` — so the value no longer parses
and the build fails.

Wrap the body in `{% raw %}`, as the rest of the docs already do. This
is only needed until a release carries the engine-side fix, which stops
parsing liquid inside markdown code.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YXKzyT7wjxop7Me8egDDqZ

This branch was successfully deployed

1 active deployment
archival.dev — be977236 Deployed Sep 15, 2026 by jesseditson via Publish to Cloudflare Pages #221
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