release: prepare v0.5.0

Advance both workspaces to the 0.5 compatibility line for the codec-8
template compression feature: databases optimized by 0.5.0 contain
rich-log blocks that pre-0.5.0 extensions refuse to decode, which is a
new stored-data forward-compatibility line, not a patch. Per the pre-1.0
policy the pairing floors move with the line: the extension now floors
servers at 0.5.0 and the servers floor extensions at 0.5.0 (release-line
guard tests updated with them). Data ABI 1, SQL-surface generation 1,
and all batch/frame formats are unchanged.

Records the 0.5.0 changelog entry with its Compatibility section,
updates the compatibility inventory (validated by query-harness
contracts), and adds the codec-8 rollback note to the upgrade guide.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: awksedgreep

CHANGELOG.md

@@ -10,10 +10,14 @@ capability document remains authoritative for a particular binary pairing.
 See the [compatibility statement](docs/COMPATIBILITY.md) and
 [upgrade guide](docs/UPGRADE.md).
 
-<!-- release-target: 0.4.2 -->
+<!-- release-target: 0.5.0 -->
 
 ## [Unreleased]
 
+No changes recorded after `0.5.0`.
+
+## [0.5.0] — 2026-08-08
+
 ### Added
 
 - CLP-style template compression for rich log message columns
@@ -27,6 +31,24 @@ See the [compatibility statement](docs/COMPATIBILITY.md) and
   when the metadata envelope dominates. Ingest/flush is unchanged; all
   prior codecs remain decodable.
 
+### Compatibility
+
+- This minor selects a new compatibility line because of stored-data
+  forward compatibility: after this extension runs rich-logs `optimize()`,
+  the database contains codec-8 blocks that pre-`0.5.0` extensions refuse
+  to decode (they fail loudly, matching the codec-6/7 posture). Reading
+  older databases is unaffected — every prior codec stays decodable, and
+  no migration runs at open.
+- Storage data ABI 1, SQL-surface generation 1, and the batch/frame
+  formats are unchanged. The extension/server pairing floors advance with
+  the line, as the pre-1.0 policy requires: the `0.5.0` extension floors
+  servers at `0.5.0` and the `0.5.0` servers floor extensions at `0.5.0`,
+  so a compatibility set upgrades as one unit. Servers load the extension
+  in-process, so any handshake-accepted pairing decodes codec 8 through
+  the loaded extension; the rollback caveat is a pre-`0.5.0` extension
+  pointed at a database already optimized by `0.5.0` (see the upgrade
+  guide).
+
 ## [0.4.2] — 2026-08-08
 
 ### Fixed
@@ -209,7 +231,8 @@ Hardened statement atomicity, savepoints, multi-process series identity,
 attached schemas, transactional drop, filesystem compaction, deadlock
 avoidance, extreme timestamps, and performance parity.
 
-[Unreleased]: https://github.com/awksedgreep/timeless-libsql/compare/v0.4.2...HEAD
+[Unreleased]: https://github.com/awksedgreep/timeless-libsql/compare/v0.5.0...HEAD
+[0.5.0]: https://github.com/awksedgreep/timeless-libsql/compare/v0.4.2...v0.5.0
 [0.4.2]: https://github.com/awksedgreep/timeless-libsql/compare/v0.4.1...v0.4.2
 [0.4.1]: https://github.com/awksedgreep/timeless-libsql/compare/v0.4.0...v0.4.1
 [0.4.0]: https://github.com/awksedgreep/timeless-libsql/compare/v0.3.0...v0.4.0

Cargo.lock

@@ -17,7 +17,7 @@ default-members = [
 resolver = "2"
 
 [workspace.package]
-version = "0.4.2"
+version = "0.5.0"
 edition = "2021"
 license = "MIT"
 

Cargo.toml

@@ -30,7 +30,7 @@ fn document() -> &'static str {
             "extension_version": env!("CARGO_PKG_VERSION"),
             "data_abi": DATA_ABI,
             "sql_surface_version": 1,
-            "minimum_server_version": "0.4.0",
+            "minimum_server_version": "0.5.0",
             "build": {
                 "commit": env!("TIMELESS_BUILD_COMMIT_RESOLVED"),
                 "target": env!("TIMELESS_BUILD_TARGET"),
@@ -185,12 +185,12 @@ mod tests {
             "the tagged v0.3.0 artifact predates the capability handshake"
         );
         assert!(
-            env!("CARGO_PKG_VERSION").starts_with("0.4."),
-            "the current extension must remain on the documented 0.4 compatibility line"
+            env!("CARGO_PKG_VERSION").starts_with("0.5."),
+            "the current extension must remain on the documented 0.5 compatibility line"
         );
         assert_eq!(
-            value["minimum_server_version"], "0.4.0",
-            "compatible 0.4 patch releases retain the 0.4.0 server floor"
+            value["minimum_server_version"], "0.5.0",
+            "compatible 0.5 patch releases retain the 0.5.0 server floor"
         );
         assert_eq!(value["data_abi"], 1);
         assert_eq!(value["sql_surface_version"], 1);

crates/timeless-ext/src/capabilities.rs

@@ -15,14 +15,14 @@ constants that enforce the handshake.
 
 | Contract key | Current value | Meaning |
 |---|---:|---|
-| `extension_workspace` | `0.4.2` | Current extension/core/dbhealth source line. |
-| `server_workspace` | `0.4.2` | Current metrics/logs/traces server source line. |
+| `extension_workspace` | `0.5.0` | Current extension/core/dbhealth source line. |
+| `server_workspace` | `0.5.0` | Current metrics/logs/traces server source line. |
 | `extension_data_abi` | `1` | Stored/public telemetry data compatibility generation. |
 | `sql_surface_version` | `1` | Advertised public SQL inventory generation. |
-| `extension_minimum_server` | `0.4.0` | Oldest server accepted by the current extension document. |
+| `extension_minimum_server` | `0.5.0` | Oldest server accepted by the current extension document. |
 | `server_data_schema` | `1` | Additive `_timeless_schema_migrations` ledger generation. |
 | `server_required_data_abi` | `1` | Data ABI required by all current signal servers. |
-| `server_minimum_extension` | `0.4.0` | Oldest extension semantic version considered by current servers. |
+| `server_minimum_extension` | `0.5.0` | Oldest extension semantic version considered by current servers. |
 
 <!-- public-compatibility-versions:end -->
 

docs/COMPATIBILITY.md

@@ -37,6 +37,17 @@ Keep the pre-upgrade backup: an older extension is not expected to understand
 the additive private schema even though stored block payloads retain their
 codec and data-ABI meaning.
 
+Starting with `0.5.0`, rich-logs `optimize()` writes template-compressed
+message blocks (codec byte 8). Nothing is rewritten at open — the new codec
+appears only as background or scheduled optimize re-encodes rich blocks — but
+once it has, a pre-`0.5.0` extension refuses those blocks with a loud decode
+error naming the unknown codec; it never returns partial or flattened rows.
+Rolling back the extension after a `0.5.0` optimize therefore requires
+restoring the pre-upgrade backup (or re-importing through the public batch
+contracts with the older binary). Upgrade every binary that opens the same
+database file as one set before allowing optimize to run, exactly as the
+invariants above require.
+
 ## 1. Inventory the current installation
 
 Record the current artifact identities and complete database paths. For a

docs/UPGRADE.md

@@ -8,7 +8,7 @@ members = [
 resolver = "2"
 
 [workspace.package]
-version = "0.4.2"
+version = "0.5.0"
 edition = "2021"
 license = "MIT"
 

servers/Cargo.lock

@@ -23,7 +23,7 @@ use serde::{Deserialize, Serialize};
 
 pub const DATA_SCHEMA_VERSION: i64 = 1;
 pub const REQUIRED_EXTENSION_DATA_ABI: u64 = 1;
-pub const MINIMUM_EXTENSION_VERSION: &str = "0.4.0";
+pub const MINIMUM_EXTENSION_VERSION: &str = "0.5.0";
 
 #[derive(Clone, Debug, Deserialize, PartialEq, Eq)]
 #[serde(deny_unknown_fields)]
@@ -540,12 +540,12 @@ mod tests {
             "the tagged v0.3.0 artifact predates the release server handshake"
         );
         assert!(
-            env!("CARGO_PKG_VERSION").starts_with("0.4."),
-            "the current servers must remain on the documented 0.4 compatibility line"
+            env!("CARGO_PKG_VERSION").starts_with("0.5."),
+            "the current servers must remain on the documented 0.5 compatibility line"
         );
         assert_eq!(
-            MINIMUM_EXTENSION_VERSION, "0.4.0",
-            "compatible 0.4 patch releases retain the 0.4.0 extension floor"
+            MINIMUM_EXTENSION_VERSION, "0.5.0",
+            "compatible 0.5 patch releases retain the 0.5.0 extension floor"
         );
     }