Skip to content

chore: Release hotdata-cli version 0.28.0 - #277

Merged
eddietejeda merged 1 commit into
mainfrom
release/0.28.0
Aug 25, 2026
Merged

eddietejeda merged 1 commit into
mainfrom
release/0.28.0

Conversation

@eddietejeda

Copy link
Copy Markdown
Contributor

Release 0.28.0

Version bump + changelog for the 0.28.0 release.

Included since 0.27.1

Notes

  • Bumps Cargo.toml, Cargo.lock, and the four skill doc version: fields to 0.28.0 (via cargo release).
  • The Rename user-facing term "managed database" to "instant database" #275 rename landed as a non-conventional commit, so git-cliff did not fold it into the generated section automatically — its [Unreleased] entry has been merged into the 0.28.0 changelog section by hand.
  • scripts/validate-changelog.py now exempts the [Unreleased] staging section from its "released sections must not be rewritten" check, since Unreleased is expected to be renamed into a concrete version at release time (previously this would have failed the changelog CI job on this PR).

After merge: scripts/release.sh finish tags v0.28.0 and triggers the dist/release workflow.

@eddietejeda
eddietejeda requested a review from a team as a code owner August 25, 2026 20:02
@eddietejeda
eddietejeda requested review from zfarrell and removed request for a team August 25, 2026 20:02
# it legitimately disappears from the base ref. Only guard released
# versions against having their bullets rewritten or dropped.
if ver.lower() == "unreleased":
continue

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: (not blocking) The exemption is the right call for the rename case, but it removes the only automated guard that [Unreleased] bullets survive a release. In this very PR the docs bullet from [Unreleased] had to be folded into 0.28.0 by hand — if that step were forgotten, or if a full git-cliff regeneration dropped it, this script would now pass silently.

A cheap way to keep both properties: instead of continue, assert each bullet line from the base [Unreleased] body still appears somewhere in the current file (any section), rather than requiring the section itself to persist. That allows the rename while still catching silent drops.

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Release mechanics check out: Cargo.toml/Cargo.lock and all four SKILL.md version: fields are bumped consistently with the pre-release-replacements list in Cargo.toml:75-81, and the folded [Unreleased] docs bullet is preserved verbatim in the new 0.28.0 section. The ver.lower() == "unreleased" comparison correctly covers both the ## [unreleased] git-cliff emits (cliff.toml:12) and the capitalized form in the file.

Two non-blocking notes inline (plus one that would not anchor: scripts/validate-changelog.py:74 — super nit, len(base_sections) now over-counts in the success message since the skipped [Unreleased] section is still included in "N section(s) preserved unchanged").

@eddietejeda
eddietejeda merged commit 261848e into main Aug 25, 2026
13 checks passed
@eddietejeda
eddietejeda deleted the release/0.28.0 branch August 25, 2026 20:05
@codecov

codecov Bot commented Aug 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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