Statewave v0.9.2 — version-consistency & SDK-readiness patch
Small stabilization patch on top of the canonical v0.9 governance release (v0.9.1). No new backend features, no API changes, no schema migrations. Operators upgrading v0.9.1 → v0.9.2 should expect zero functional difference.
What changes in this server release
pyproject.tomlbumped from0.9.0to0.9.2(#171) — closes the pyproject/tag drift introduced when0.9.0was bumped ahead of the actual v0.9 work. Both the v0.9.0 (stub, superseded) and v0.9.1 (canonical) tags reported0.9.0frompip show statewave; v0.9.2 closes that drift sopip show statewavereports a version matching the published tag.
That is the entire server-side change. Zero code, schema, or behaviour difference vs. v0.9.1.
Coordinated companion PRs in the same stabilization patch
These ship as additive patch releases on their own repos:
statewave-pyv0.10.1 (closes #169) — addsverify_receipt(receipt_id)andreplay_receipt(receipt_id)to bothStatewaveClient(sync) andAsyncStatewaveClient(async) with typed Pydantic return models (ReceiptVerifyResult,ReceiptReplayResult) and a dedicatedStatewaveUnreplayableError(reason)for HTTP 422 refusal codes. README governance section refreshed; PyPIDevelopment StatusAlpha → Beta.statewave-tsv0.10.1 (closes #170) — addsverifyReceipt(receiptId)andreplayReceipt(receiptId)toStatewaveClient. TheReceiptinterface gains the v0.9 governance fields (policySnapshot,receiptSignatureAlgorithm, plusregionif missing) and a discriminatedStatewaveUnreplayableErrormirrors the Python error type. Version-aligned withstatewave-pyv0.10.1.statewave-examples— correctstry-it.shinstall command:pip install statewave-py(the GitHub repo name) →pip install statewave(the published package name).statewave-web— refreshes three stale v0.9-era strings: ProductPage auto-labeling description ("planned" → "shipped"),llms-full.txtGovernance version tag (v0.8→v0.8+), proof-figure counts where re-counted locally against current main. No broader proof-figure sweep in this patch.
Out of scope (explicit)
No new backend features. No admin identity, bulk label promotion, visual policy editor, federated cross-region audit, second-region deployment, RLS, byte-for-byte replay, or proof-figure workspace-wide sweep — all deferred to later v0.9.x patches or post-1.0 per the v0.9.x → v1.0 roadmap.
Upgrade
pip install --upgrade statewave==0.9.2 or docker pull statewavedev/statewave:0.9.2. Zero migrations to run; database state is unchanged from v0.9.1.
For SDK upgrade, wait for statewave-py / statewave-ts v0.10.1 (landing alongside this server release).