Repository navigation
v0.4.55
Weft 0.4.55
Release scope
This release changes the Python distribution name from weft-sql to
umf-weft. The Python import remains weft; compiler protocols, backend
registrations and SQL behavior retain the qualified 0.4.54 compiler base,
including G02 and the integrated Unity/raw-read fixes. Version and distribution
metadata change, so every released wheel requires fresh qualification.
The immutable GitHub release
and public PyPI publication passed their bounded release gates on 2026-10-27.
Source and tag target ea0fef0209aaf8e08ef165b6afe00b408873354f bind all three
fresh wheels. Actual OIDC upload, public archive-byte comparison and a fresh
Ubuntu public-index installation/import passed in
run 40424569422.
Raw receipts and verification retain exact
wheel, native-module and artifact hashes. This later evidence update does not
modify the frozen tag or its assets.
Audience and channels
Python consumers and dependency maintainers receive the change through the
GitHub release and PyPI project. Hosts retain responsibility for execution,
transactions, authorization and their own installed-package admission gates.
Changes and fixes
The release uses Actions for all three wheel targets: Linux x86_64, Linux ARM64
and macOS ARM64. The macOS producer checks the installed wheel and compares nine
frozen refusal responses across Rust, installed Python and real Chromium WASM.
Linux producers check exact installed packaging only. No sdist is produced.
The existing gated PyPI workflow publishes the qualified bytes using OIDC.
The selected wheel composition retains WFT-BACKEND-VERSION for the three
older Databricks requests and WFT-BACKEND-MISSING for the other six vectors.
The generic corpus's default-registry expectations remain unchanged; the
producer checks this selected composition and requires complete Rust/Python/WASM
response-byte parity.
Breaking changes and required actions
New dependency declarations use umf-weft==0.4.55. Keep
import weft and existing protocol identifiers unchanged. Replace the old
distribution in a fresh environment; do not install both distributions together,
because they provide the same import package. Existing immutable weft-sql
releases and consumers pinned to them retain their original names and evidence.
Migration or rollback guidance
The public archive hashes match the qualified GitHub assets. Consumers remain
pinned until their owning integration gates pass. To hold an upgrade,
retain the previously qualified environment and dependency pin. Recreate that
environment to roll back; do not overwrite a released wheel or relabel an old
receipt as evidence for this distribution.
Known issues and support
The nine macOS vectors establish refusal-response parity only. They do not
qualify positive query compilation or native PostgreSQL execution. Linux checks
establish packaging identity only. Separate compiler/native evidence retains its
original versions, source and scope; this release adds no production executor,
managed database, generated-client or security authority claim. Consumer
admission remains a separate gate; the fresh public Ubuntu install passed.
The broader compiler conformance jobs were still running when this release
record was captured; their results are not counted as complete by the bounded
distribution proof.