Skip to content

release: 0.2.1 - #11

Merged
eddietejeda merged 1 commit into
mainfrom
bump/0.2.1
Sep 9, 2026
Merged

release: 0.2.1#11
eddietejeda merged 1 commit into
mainfrom
bump/0.2.1

Conversation

@eddietejeda

Copy link
Copy Markdown
Contributor

Version bump to 0.2.1 so the tag-triggered release workflow (merged in #10, after v0.2.0 was tagged) can publish the first PyPI release. After merge: tag v0.2.1 on main and push it.

Version bump so the tag-triggered release workflow (added after
v0.2.0 was tagged) can publish the first PyPI release.
Comment thread pyproject.toml
[project]
name = "dbt-hotdata"
version = "0.2.0"
version = "0.2.1"

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 ## [0.2.1] section to CHANGELOG.md (not blocking).

CHANGELOG.md line 3 states that all notable changes are documented in that file, and pyproject.toml line 30 publishes that file as the project Changelog URL. PyPI users of 0.2.1 will find no entry for the version they installed. A one-line entry noting the release-workflow republish is enough.

@@ -1 +1 @@
version = "0.2.0"
version = "0.2.1"

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: uv.lock line 327 still records version = "0.2.0" for the dbt-hotdata editable package (not blocking).

CI runs plain uv sync, which rewrites the lock, so no check fails. Run uv lock and commit the result to keep the committed lock in sync.

@eddietejeda
eddietejeda merged commit 4fa01d8 into main Sep 9, 2026
4 checks passed
@eddietejeda
eddietejeda deleted the bump/0.2.1 branch September 9, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant