chore: release hotdata-dlt-destination v0.14.0 - #82
Conversation
`update_changelog.py` only preserves the guide comment when it is the FIRST thing in the [Unreleased] body (`_GUIDE_RE` is anchored with \A). The notes for #80 and #81 were inserted above it, so `prepare` treated it as part of the notes and moved it down into the released 0.14.0 section -- leaving [Unreleased] bare and putting the authoring guide inside the payload `extract-changelog.py` hands to the GitHub Release. Moved back under [Unreleased]. Verified both ways: extracting 0.14.0 no longer carries the guide, and a simulated 0.15.0 prepare preserves it.
There was a problem hiding this comment.
Prior blocking-adjacent finding resolved: the style guide now sits directly under ## [Unreleased] (CHANGELOG.md:8-20), so _GUIDE_RE's \A anchor will match it on the next release.sh prepare, and the 0.14.0 section body no longer carries it. Version bump is consistent across pyproject.toml and uv.lock. One super nit inline. CI checks were still queued/in progress when this review ran, so treat the release-metadata check as unverified here.
There was a problem hiding this comment.
Both prior threads are resolved in the code: the style guide is back directly under ## [Unreleased] (CHANGELOG.md:8-20) where _GUIDE_RE's \A anchor will find it, and the stray blank line before ## [0.13.2] is gone. The resulting file matches what update_changelog.py itself would emit — fresh [Unreleased] with guide, notes moved verbatim into the dated section.
Version bump is consistent: pyproject.toml and uv.lock both at 0.14.0, no stale 0.13.2 references anywhere else in the tree. Minor bump is right for the new dlt source.
Check release metadata / Verify changelog matches version bump passed. CI / Test (Python 3.12) was still pending when this review started, so merge on that going green.
Summary
Release hotdata-dlt-destination v0.14.0.
Checklist
pyproject.tomlCHANGELOG.mdupdatedAfter merge, run
./scripts/release.sh publishfrom a cleanmaincheckout.