Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,22 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.2.2] - 2026-09-09

### Changed

- Raised the Hotdata SDK ceilings to `hotdata<0.10` and
`hotdata-framework<0.15`, allowing the newest coherent pair (hotdata 0.9.x +
framework 0.14.x). Verified against a live workspace: full dbt run and test
suite pass with hotdata 0.9.1 + hotdata-framework 0.14.0.

## [0.2.1] - 2026-09-09

### Changed

- Version bump only, to produce the first PyPI release via the tag-triggered
release workflow.

## [0.2.0] - 2026-09-08

### Added
Expand Down
2 changes: 1 addition & 1 deletion dbt/adapters/hotdata/__version__.py
Original file line number Diff line number Diff line change
@@ -1 +1 @@
version = "0.2.1"
version = "0.2.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

super nit: add a test asserting this version string equals the pyproject.toml version. No check ties the two strings today, and .github/workflows/release.yml:15-22 compares the git tag against pyproject.toml only. A future bump that misses this file publishes a wheel where dbt --version reports a stale adapter version. (not blocking)

11 changes: 7 additions & 4 deletions pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[project]
name = "dbt-hotdata"
version = "0.2.1"
version = "0.2.2"
description = "dbt adapter for Hotdata instant databases."
readme = "README.md"
license = "MIT"
Expand All @@ -18,9 +18,12 @@ dependencies = [
"dbt-common>=1.14,<2",
"dbt-core>=1.10,<2",
# Instant-database lifecycle + retry-wrapped client come from the shared
# Hotdata SDK pair, same floors as hotdata-dlt-destination.
"hotdata>=0.8.0,<0.9",
"hotdata-framework>=0.9.0,<0.10",
# Hotdata SDK pair. Ceilings track the newest tested pair (hotdata 0.9.x +
# framework 0.14.x, verified against a live workspace); framework releases
# declare their own compatible hotdata range, so the resolver picks a
# coherent pair within these bounds.
"hotdata>=0.8.0,<0.10",
"hotdata-framework>=0.9.0,<0.15",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: add a CI job that runs uv sync --resolution lowest-direct before pytest. The extra job keeps the wide range intact and exercises the floors.

.github/workflows/ci.yml:20 runs plain uv sync against uv.lock, so CI tests only hotdata 0.9.1 + framework 0.14.0. Before this change the lock sat on framework 0.9.0, which equalled the declared floor. After this change the declared floors, hotdata 0.8.0 and framework 0.9.0, stay unexercised across five framework minors.

Failure scenario: a later commit calls an API added in framework 0.11. CI stays green on 0.14.0. A consumer whose environment caps hotdata-framework at 0.9.x installs dbt-hotdata, and the adapter raises ImportError or AttributeError on the first model. (not blocking)

"pyarrow>=14",
]

Expand Down
18 changes: 9 additions & 9 deletions uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading