Skip to content

Xsl3 1.2.0

Choose a tag to compare

@skuirrels skuirrels released this 02 Nov 19:18
· 79 commits to main since this release
3ea172a

Xsl3 1.2.0

Release date: 2 November 2026. This release makes strict streamability analysis follow the XSLT 3.0
rules for unions and records P7 phase A. Full streaming remains experimental and unsupported.

Breaking change

A union of two striding operands is crawling (XSLT 3.0 §19.8.8.4), even when both are child steps from
the same parent, such as (/BOOKLIST/ITEM | /BOOKLIST/MAGAZINE)/PRICE. Earlier releases treated such
unions as striding. That is an extension, which §19.10 allows only when the user asks for one, and there
was no way to ask.

XsltSettings.Streamability = Strict is the default, so a declared-streamable template, mode,
xsl:source-document or other construct that relied on the extension, and compiled with 1.1.7, now
raises XTSE3430 at compile time. Either:

  • select XsltStreamabilityMode.Fallback, which runs the construct with ordinary tree-based execution, or
  • write the selection as one striding step, for example /BOOKLIST/*[self::ITEM or self::MAGAZINE]/PRICE.

See the migration guide.

Other changes

  • P7 phase A evidence: retained-state bounds for xsl:iterate parameters, adjacent grouping and
    node-valued accumulators through both public APIs, and failing-prong cancellation in a compiled
    xsl:fork (later prongs are cancelled; earlier prongs finish so the error follows declaration order).
  • CI accounts for the original S3-S7 conformance exits on every run and fails if a stage regresses
    against unstreamed execution or a strict failure has no recorded disposition.
  • The XSLT 3.0 test runner honours directory collections, so W3C merge-039 runs and passes.

Verification and limits

W3C strict streaming: 2,696 of 2,712 cases pass (99.41%) with every failure recorded in
the phase A dispositions; sx-union-202 now passes and
sx-union-315, whose fixture relies on the removed extension, fails. Full .NET 8 and .NET 10 unit suites,
upstream, differential, W3C, NativeAOT and the performance gate run in
PR #28 checks. The
release workflow builds and tests the
tagged source before the owner's required NuGet deployment review.

Default execution stays tree-based and supports-streaming remains no. The original streaming RSS and
throughput gates are still unmet; this release does not claim full P7 completion. Five other compiler
streamability extensions remain on and are due for the same §19.10 review (see
P7 phase A).

Update Xsl3, Xsl3.Build and Xsl3.Cli together to 1.2.0 and regenerate saved stylesheets
using matching compiler/runtime packages.