ci: create the GitHub release from the CHANGELOG section on tag push - #1
Merged
Conversation
Four tags shipped to PyPI on 2026-09-01 while the repo page still said Latest v0.3.1. The notes already live in CHANGELOG.md; this derives the release from them (title from the heading, body from the section) so a tag is never silently unreleased, and fails the run if the section is missing rather than publish an empty release. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
On 2026-09-01 v0.4.0 through v0.7.0 went to PyPI and the repo page still said Latest: v0.3.1. A tag without a release is the "does anyone maintain this?" signal, and the notes were already written, in
CHANGELOG.md.I backfilled the four missing releases by hand from their CHANGELOG sections (same source the v0.3.1 release body came from). This workflow makes that the default for the next tag.
What it does
On
pushof av*tag: awk out the## <tag> ...section ofCHANGELOG.md, title from the heading with the trailing date stripped, body from the section,gh release create --verify-tag. If the section is missing the run fails with a pointer, instead of publishing an empty release.Tested the extraction locally against the current file:
v0.7.0-> titlev0.7.0 — a guess may not delete a window, 16 body lines;v0.3.1-> titlev0.3.1, 27 lines; a tag with no section fails.Nothing else changes: PyPI stays manual,
checkis untouched.