Release 0.3.0: legaldown-validator 0.4.0

CONFORMANCE.md

@@ -1,8 +1,8 @@
 # Conformance
 
-`legaldown-render` targets **Level 2 — Rendering** of the LegalDown specification **0.2**
-(§17.3), as 0.2.0 did. Core parsing and validation come from `legaldown-validator` 0.4 (0.3.0 up
-to `legaldown-render` 0.2.0), which claims Level 1 — Core. Its own [CONFORMANCE.md](https://github.com/ForLegalAI/legaldown-validator/blob/main/CONFORMANCE.md)
+`legaldown-render` 0.3.0 targets **Level 2 — Rendering** of the LegalDown specification **0.2**
+(§17.3). Core parsing and validation come from `legaldown-validator` 0.4, which claims Level 1
+— Core. Its own [CONFORMANCE.md](https://github.com/ForLegalAI/legaldown-validator/blob/main/CONFORMANCE.md)
 lists the Core rules it covers.
 
 It is checked against the specification's own examples and fixtures corpus (`tests/conformance/`):

docs/decisions/0004-html-first.md

@@ -38,3 +38,5 @@ The leading option is WeasyPrint. It will be decided with a spike when v0.4 star
 - The first release has a small dependency footprint and fast tests.
 - The HTML writer's markup should be designed with print CSS in mind from the start, so the PDF
   path can reuse it.
+- 2026-10-03: v0.3 became the release built on legaldown-validator 0.4.0, so `docx` moves to
+  v0.4 and `pdf` to v0.5 (see the [roadmap](../roadmap.md)).

docs/roadmap.md

@@ -34,7 +34,7 @@ here.
 - `text` and `html` writers; the `legaldown-render` CLI
 - Golden tests, and a conformance run over the specification's examples and fixtures
 
-### v0.2 — Templates with answers (this release)
+### v0.2 — Templates with answers
 
 - Rendering with an answers set, through the core package's assembly (U4b)
 - `--answers answers.yaml` on the CLI
@@ -43,13 +43,20 @@ here.
   diagnostics with line numbers
 - Built on `legaldown-validator` 0.3.0; the first release on PyPI
 
-### v0.3 — DOCX
+### v0.3 — Validator 0.4.0 (this release)
+
+- Built on `legaldown-validator` 0.4.0 and only its public API (`legaldown`, `legaldown.syntax`,
+  `legaldown.grammar`); `validator_bridge.py` is removed (U3)
+- A deprecated validator API fails the tests, so a release never calls what the next minor
+  version removes
+
+### v0.4 — DOCX
 
 - `docx` writer behind the `[docx]` extra
 - To decide first: static numbers, or Word-native numbering with `REF` fields
   ([ADR 0004](decisions/0004-html-first.md))
 
-### v0.4 — PDF
+### v0.5 — PDF
 
 - Choose the engine ([ADR 0004](decisions/0004-html-first.md)). The leading option is WeasyPrint
   on the HTML writer; its print stylesheet already exists

src/legaldown_render/__init__.py

@@ -21,7 +21,7 @@
 from .errors import DocumentError, InternalError, RenderError, RenderRefused
 from .style import Style, StyleError, builtin_styles, dump_style, load_style
 
-__version__ = "0.2.0"
+__version__ = "0.3.0"
 
 #: The LegalDown specification version this renderer targets.
 SPEC_VERSION = "0.2"

tests/golden/features.default.html

@@ -4,7 +4,7 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>Services Agreement</title>
-<meta name="generator" content="legaldown-render 0.2.0">
+<meta name="generator" content="legaldown-render 0.3.0">
 <style>
 .ld-document { margin: 0 auto; padding: 2rem 1rem; }
 .ld-title { font-size: 1.5em; text-align: center; margin: 0 0 0.25em; }

tests/golden/template.default.html

@@ -4,7 +4,7 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>Consulting Agreement with [_____]</title>
-<meta name="generator" content="legaldown-render 0.2.0">
+<meta name="generator" content="legaldown-render 0.3.0">
 <style>
 .ld-document { margin: 0 auto; padding: 2rem 1rem; }
 .ld-title { font-size: 1.5em; text-align: center; margin: 0 0 0.25em; }