From 8178d206709de9c298ab82385c00578df0b247a6 Mon Sep 17 00:00:00 2001
From: Shefeek Jinnah <shefeek@hotdata.dev>
Date: Wed, 23 Sep 2026 16:19:50 +0530
Subject: [PATCH 1/2] chore: release v0.19.0

---
 CHANGELOG.md | 3 +++
 Cargo.toml   | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index ff3c922..63b3e06 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+
+## [0.19.0] - 2026-09-23
+
 ### Changed
 
 - feat(databases): add description field to fork lineage
diff --git a/Cargo.toml b/Cargo.toml
index 7d4e73f..11ea937 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "hotdata"
-version = "0.18.1"
+version = "0.19.0"
 authors = ["developers@hotdata.dev"]
 description = "Powerful data platform API for datasets, queries, and analytics."
 license = "MIT"

From 4f374bfdcc7a6a772c5c02336e8c81647eb696de Mon Sep 17 00:00:00 2001
From: Shefeek Jinnah <shefeek@hotdata.dev>
Date: Wed, 23 Sep 2026 16:25:28 +0530
Subject: [PATCH 2/2] docs: write the 0.19.0 changelog and bump README pins

---
 CHANGELOG.md | 31 +++++++++++++++++++++++++++++--
 README.md    |  6 +++---
 2 files changed, 32 insertions(+), 5 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 63b3e06..3c933a2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,10 +10,37 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [0.19.0] - 2026-09-23
 
+### Added
+
+- **Fork descriptions.** `ForkDatabaseRequest` has an optional `description`.
+  It records why the fork was taken, and you can set it only at fork time.
+  The server returns it on `ForkedFromInfo`, `LineageAncestorInfo` and
+  `LineageForkInfo`. On an ancestor entry, it describes the fork taken from
+  that ancestor (the next generation down).
+- **Constant-per-key after table creation.** Two new operations change the
+  declaration on an existing table: `set_database_table_constant_per_key` and
+  `set_managed_table_constant_per_key`. Both take an
+  `UpdateManagedTableRequest` and return a
+  `ManagedTableConstantPerKeyResponse`. `TableInfo` now reports
+  `constant_per_key`. `JobType` has a new `TableConstantsUpdate` variant.
+- **Vector index precision.** `CreateIndexRequest` has an optional
+  `vector_precision` field of type `VectorPrecision` (`float64`, `float32`,
+  `float16` or `float8`). `IndexInfoResponse` and `IndexEntryResponse` report
+  it.
+
 ### Changed
 
-- feat(databases): add description field to fork lineage
-- chore(databases): simplify fork error description
+- **Breaking:** `key_determines` is now `constant_per_key` on
+  `AddManagedTableDecl`, `AddManagedTableRequest` and
+  `DatabaseDefaultTableDecl`. This matches the server, which rejects the old
+  name.
+- **Breaking:** some generated models have new public fields, for example
+  `ForkDatabaseRequest.description` and `TableInfo.constant_per_key`. Code
+  that builds these structs as literals must set the new fields. To avoid
+  this in the future, start from `::new()` or `..Default::default()`.
+- The API documentation now covers more detail: fork error cases,
+  `default_connection_id` and catalog attachment rules, the 16 GiB upload
+  limit, and case matching in database name search.
 
 ## [0.18.1] - 2026-09-18
 
diff --git a/README.md b/README.md
index ba0446f..f0c0e9f 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@ Add the crate to your `Cargo.toml`:
 
 ```toml
 [dependencies]
-hotdata = "0.18"
+hotdata = "0.19"
 tokio = { version = "1", features = ["macros", "rt-multi-thread"] }
 ```
 
@@ -29,7 +29,7 @@ By default the crate builds against `native-tls`. To use `rustls` instead:
 
 ```toml
 [dependencies]
-hotdata = { version = "0.18", default-features = false, features = ["rustls"] }
+hotdata = { version = "0.19", default-features = false, features = ["rustls"] }
 ```
 
 ## Authentication
@@ -207,7 +207,7 @@ Query results can be fetched as an [Apache Arrow](https://arrow.apache.org/) IPC
 
 ```toml
 [dependencies]
-hotdata = { version = "0.18", features = ["arrow"] }
+hotdata = { version = "0.19", features = ["arrow"] }
 ```
 
 `ArrowResult` hands back `arrow` types, so a crate that names them must depend