From fef8520d6864ec912badeefebabcaa32c3123ef4 Mon Sep 17 00:00:00 2001 From: Mihaela Mihaljevic Date: Sat, 27 Jun 2026 21:22:15 +0200 Subject: [PATCH] chore(release): stamp 0.4.8 (#316) Move the [Unreleased] section to [0.4.8] - 2026-06-27. No source changes. 0.4.8 collects the interactive-safety depth-recursion program: every walk over the value-Node/TreeNode model, the parser and XPath result ordering, the canonical, XInclude, HTML, and XSLT serialization paths, and the XSLT transformation engine itself are now iterative, so parsing, validating, querying, transforming, and serializing adversarial or deeply-nested input no longer overflows the stack. Also includes the xpointer string-range() and XSLT id() quadratic fixes. --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 49c3fed..de205ee 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +## [0.4.8] - 2026-06-27 + ### Removed - Five unused internal schema-consistency wrappers (`idAttributeErrors`, `consistencyErrors`, `postNamedTypeErrors`, `structureErrors`, `includeCompositionErrors`) that returned `[String]` reason lists, along with the now-orphaned `postCompileErrors(schema:context:containers:namedTypes:)` overload and the `SchemaCompileNamedTypes` struct it consumed. None had callers; the `XSDParser.consistencyErrors` overload was shadowed by the distinct, still-live `Validation.XSDSchema.consistencyErrors` (a different signature returning `ValidationError`), which is why a name-only search first read it as used. The located-diagnostic API (the `*Findings` functions returning `SchemaLocatedFinding`, and `Validation.XSDSchema` returning `ValidationError`) superseded all of them. Removing them deletes dead code with no behavior change; the live `*Findings` and `Validation.XSDSchema` functions are unchanged. A stale doc-comment reference to the renamed `userTypeValueConstraintErrors` (now `userTypeValueConstraintFindings`) was corrected at the same time.