Engine Changelog

Key engine changes in recent releases and what they mean for templates.

This page highlights recent releases that materially changed template behavior.

Release `v0.1.7` (`2026-04-29`)

Fixed modern template infrastructure generated by template update:
- content.local_dir is now resolved relative to config location (for example .np/config.yaml + ../content).
- modern deploy workflow resolves absolute content path from config before content-repo sync.
Result: modern templates with custom content paths no longer lose media/content during CI sync.

Obsidian markdown support became first-class in engine runtime/build:
- callouts (> [!note], folded variants),
- inline syntax (==mark==, ~sub~, ^sup^),
- footnotes and math wrappers,
- safer wikilink/embed preprocessing outside fenced and inline code.
Added markdown diagnostics:
- validate --markdown
- --markdown-strict
- --markdown-format text|json
- --output <path>
Added template tooling:
- notepub template check
- notepub template update (--apply for writes)
Added settings/overrides baseline for templates:
- settings: is first-class input,
- optional note overrides via overrides.site_note / overrides.interface_note,
- compatibility mode compat_mode: auto|modern|legacy.
SEO/runtime fixes:
- /search page rendering uses search note route/meta/body when present,
- sitemap compatibility (sitemap-index.xml + sitemap.xml),
- canonical trailing-slash redirect behavior improved in serve,
- local media serving now accounts for settings-driven assets and sibling ../media.

Keep CI binary pin current (now v0.1.7).
For template repos, gate changes with a matrix across:
- compat_mode (auto|modern|legacy)
- notes presence (present|absent)
- source mode (local|s3)
Prefer engine-native Obsidian behavior over custom markdown rewrite scripts.