Skip to content

chore: release hotdata-runtime v0.2.1 #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eddietejeda merged 3 commits into from
May 25, 2026
Merged

chore: release hotdata-runtime v0.2.1 #12

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8de34cc
chore: release v0.2.1
eddietejeda May 25, 2026
c39dca2
chore: improve changelog notes for v0.2.1
eddietejeda May 25, 2026
1143e1c
chore: update lockfile for v0.2.1
eddietejeda May 25, 2026
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
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]


## [0.2.1] - 2026-05-24

### Changed

- Release 0.2.1
Copy link
Copy Markdown

@claude claude Bot May 25, 2026

Choose a reason for hiding this comment

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

This changelog entry is the update_changelog.py fallback boilerplate that gets emitted when [Unreleased] is empty (see scripts/update_changelog.py:21-25). But there is a real, user-visible change in this release: commit 629b018 (feat: add database parameter to execute_sql for managed database scoping, #11) added an optional keyword-only database parameter to execute_sql that resolves to a managed database ID and is sent as the X-Database-Id header. That is exactly the kind of API addition consumers reading the changelog need to know about.

Please replace the placeholder with a description of what actually shipped, e.g.:

Suggested change
## [0.2.1] - 2026-05-24
### Changed
- Release 0.2.1
## [0.2.1] - 2026-05-24
### Added
- `execute_sql` accepts an optional keyword-only `database` parameter. When provided, the name is resolved to a managed database ID once and sent as the `X-Database-Id` header on each query attempt. Without it, behavior is unchanged.

Also worth a look: since this is a new feature (feat:) and the project states it follows SemVer, a minor bump (0.3.0) is the conventional choice over a patch. The repo's prior history is a bit mixed (0.1.0 → 0.1.1 also shipped a feature as a patch), so this is a judgment call — flagging in case it was unintentional.


## [0.2.0] - 2026-05-24

### Changed
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "hatchling.build"

[project]
name = "hotdata-runtime"
version = "0.2.0"
version = "0.2.1"
description = "Workspace/session runtime primitives for Hotdata integrations"
readme = "README.md"
requires-python = ">=3.10"
Expand Down
Loading