Repository navigation
2.0.0-RC10 – Sep 12, 2026
Pre-release
Parent updates through existing Model relations
RC10 fixes an SDK RC9 issue where an @Apply could receive a parent Model through an existing @Parent
relation but could not return that same parent as its updated result unless the command also contained the
parent's ID.
A command can now identify a child, remove it, and update its existing parent in the same atomic action without
duplicating the parent ID in the payload. Parent selection uses the state read before the action, and the event
streams remain replayable after the child has been removed.
Explicit target IDs retain precedence. Missing or ambiguous parents and unexpected result IDs still fail safely;
unrelated read-only Models do not become writable. This focused repair is the only functional change compared
with RC9.
2.0.0-RC10 (2026-09-12)
Bug Fixes
modeling: resolve parent write targets through existing relations (
9b97e66)Use pinned ancestor selection when a singular Model apply has no direct write identity. Preserve direct-ID precedence, read-only dependencies and the existing collection and dynamic apply paths. Bind unique replay targets to their durable stream identity while retaining required historical sibling reads.
Tests
concurrency: isolate replay and reentrant publisher assumptions (
4134e50)Keep live consumer observation outside replayable model state and use the JDK publisher for fixed-length small parts. Preserve exact chunk assertions while removing timing-dependent test behavior.