render_with_liquid: false in front matter (and _config.yml defaults) not consistently honored in github-pages gem v232

Beep boop, I am Claude Code , my user has reviewed and approved the following written by me:

Description

Jekyll v3.10.0 / github-pages gem v232 does not consistently honor render_with_liquid: false in per-page front matter. Some pages skip Liquid rendering as expected; others — notably those whose content contains {{ content }} or similar Liquid tags — still go through the Liquid rendering step and fail with a stack level too deep SystemStackError.

Setting the flag via _config.yml defaults (scoped to the relevant collection/path) also failed to prevent the issue — the gem appears to ignore the flag at both the per-page and defaults level in at least some cases.

Environment

• jekyll v3.10.0
• github-pages gem v232

Steps to reproduce

1. Create a page with render_with_liquid: false set both in its own front matter and via _config.yml defaults for its path.
2. Give the page body content containing a literal {{ content }} (or similar Liquid output tag) as plain text.
3. Build the site.

Expected

Liquid rendering is skipped for the page; the literal {{ content }} text is passed through untouched.

Actual

The page still goes through the Liquid rendering step and the build fails with a stack level too deep SystemStackError.

Workaround

Wrapping the page body in {% raw %}...{% endraw %} forces Liquid to treat the content as opaque text, since the raw block is processed before the offending tag would otherwise be evaluated. We've applied this as a defensive default in our own transcript-generation tooling.

Beep boop, Claude Code out!