hotdata-framework 0.6.1__tar.gz → 0.6.2__tar.gz

{hotdata_framework-0.6.1 → hotdata_framework-0.6.2}/CHANGELOG.md

@@ -8,11 +8,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 
+## [0.6.2] - 2026-07-08
+
+### Changed
+
+- Repository text cleanup: the changelog and test docstrings no longer reference external issue trackers. No functional changes; 0.6.2 is byte-identical to 0.6.1 in package code.
+
 ## [0.6.1] - 2026-07-08
 
 ### Fixed
 
-- `ManagedDatabaseClient.fetch_table` now carries the `X-Database-Id` scope header on the result poll, the query-run poll, and the Arrow fetch — not only on the query submit. Results of database-scoped queries are themselves database-scoped, so every read against an existing synced table (merge/append loads, dlt state restore) failed with `400: Bad Request` once the table had data (dlthubworker#70).
+- `ManagedDatabaseClient.fetch_table` now carries the `X-Database-Id` scope header on the result poll, the query-run poll, and the Arrow fetch — not only on the query submit. Results of database-scoped queries are themselves database-scoped, so every read against an existing synced table (merge/append loads, dlt state restore) failed with `400: Bad Request` once the table had data.
 - API error messages now include the response body (flattened, truncated to 500 chars). `400: Bad Request` alone hid the server's actual explanation.
 
 ### Changed

{hotdata_framework-0.6.1 → hotdata_framework-0.6.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hotdata-framework
-Version: 0.6.1
+Version: 0.6.2
 Summary: Python framework for building Hotdata integrations: workspace/session runtime, query execution, and managed databases
 Project-URL: Homepage, https://www.hotdata.dev
 Project-URL: Documentation, https://www.hotdata.dev/docs

{hotdata_framework-0.6.1 → hotdata_framework-0.6.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "hotdata-framework"
-version = "0.6.1"
+version = "0.6.2"
 description = "Python framework for building Hotdata integrations: workspace/session runtime, query execution, and managed databases"
 readme = "README.md"
 requires-python = ">=3.10"

{hotdata_framework-0.6.1 → hotdata_framework-0.6.2}/tests/test_errors.py

@@ -1,8 +1,7 @@
 """Error message construction: the API's response body must survive.
 
 "400: Bad Request" alone is undebuggable; the body carries the server's
-actual explanation (e.g. which header was missing). Regression for the
-opaque load failures in dlthubworker#70.
+actual explanation (e.g. which header was missing).
 """
 
 from __future__ import annotations

{hotdata_framework-0.6.1 → hotdata_framework-0.6.2}/tests/test_managed_client.py

@@ -107,8 +107,7 @@ def test_fetch_table_carries_database_scope_on_result_reads(
     hotdata 0.6.0 SDK exposes ``x_database_id`` on all three.
 
     Regression: reruns/append loads against an existing synced table failed
-    with an opaque ``400: Bad Request`` (dlthubworker#70) because both reads
-    omitted the scope.
+    with an opaque ``400: Bad Request`` because both reads omitted the scope.
     """
     result_scopes: list[str | None] = []
     arrow_scopes: list[str | None] = []

{hotdata_framework-0.6.1 → hotdata_framework-0.6.2}/uv.lock

@@ -101,7 +101,7 @@ wheels = [
 
 [[package]]
 name = "hotdata-framework"
-version = "0.6.1"
+version = "0.6.2"
 source = { editable = "." }
 dependencies = [
     { name = "hotdata" },