Repository navigation
Weft v0.4.44
Weft 0.4.44 presence/Graph and UMF 0.10 raw-carrier release
This release packages the existing issued CurrentPresencePreparation, model and
Graph requirements, and original PostgreSQL presence lower/check APIs alongside
all six standard 0.4.41 features. It includes the
current-presence-graph-requirements-candidate feature and its declared
prerequisites; Python/Cargo versions are canonical 0.4.44.
Source starts from public main 0a9b3560 and includes UMF 0.10.0 schema
admission and raw PostgreSQL UUID/128-bit carrier changes. The raw-read profile
accepts original UMF 0.8.0 and 0.10.0 source documents; UUID and bits128 columns
are admitted only for postgresql18 and lakebase18. UUID maps to PostgreSQL
uuid and bits128 maps to bytea. Selected UMF 0.10 elements outside the
established raw scalar subset, including semantic type references, non-empty
extension content, and unsupported Record reference roles, remain refused. The
source document and its pin are retained. No additional adapters, managed
database execution, or native authority are implied.
No unmerged aggregate, term-filter, UC search or managed-mutation semantics are
included. Their separate preserved development candidates remain a later
tranche. The approved bounded plan is retained by Truss at commit
933e47a9381fe9b8294200b989360b35c017bc56, under its current-graph-authority
evidence.
The catalog-capacity wheel gate preserves the 0.4.42 canonical result receipt
after removing only the declared engine-navigation language profile addition.
It also asserts that weft-sql/0.2.0 /
weft-ir/engine-navigation/0.1 is present exactly once for each of the 15
operations. All previous packaging, query ABI, Date, Decimal12, native70,
current Databricks, refinement and SDK gates remain required on all five
platforms.
Release pins retain exact source, declared workspace feature closure,
wheel/native module/shim hashes and report identities. Publication follows
completed source review and local checks, then the existing exact-tag
five-platform wheel and automatic publication gates. Inspect the actual public
assets and digests before Truss enrollment. The failed v0.4.43 candidate is
preserved as an immutable tag and has no published release assets.
Candidate compiler APIs grant no native admission or protected activation.
Truss owns fresh scalar/Graph cohort registration and real local/hosted
qualification before changing its default compiler pin. Unsupported target
native Graph support is not inferred from wheel availability. SDK temporal
qualification remains HELD.