Skip to content

Create GitHub Releases from the release workflow - #165

Merged
gonzalocasas merged 2 commits into
mainfrom
ci/create-github-release
Nov 10, 2026
Merged

gonzalocasas merged 2 commits into
mainfrom
ci/create-github-release

Conversation

@gonzalocasas

@gonzalocasas gonzalocasas commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

The release workflow only uploaded to PyPI, so v2.0.1 and v2.1.0 got tags and PyPI releases but no GitHub Release. The 2.0.0 Release was created by hand.

After the PyPI upload, the workflow now handles the GH release creation automatically.

The release workflow only published to PyPI, so v2.0.1 and v2.1.0 got
tags but no GitHub Release (2.0.0 had been created by hand). After the
PyPI upload, extract the version's section from CHANGELOG.rst, convert
it to Markdown, and create the release with the sdist/wheel attached and
GitHub's generated notes (contributors, full changelog link) appended.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The changelog to Markdown conversion moves from an inline Python heredoc
in release.yml to an `invoke release-notes` task in tasks.py, next to the
other changelog tooling. It can now be run locally to preview the notes.

The conversion now fails on lines it cannot convert (paragraphs, text
outside a group) and on sections without entries, instead of silently
dropping them. Nested bullets are kept.

The notes are extracted before building and publishing, so a missing or
broken changelog section stops the release before it reaches PyPI.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@gonzalocasas
gonzalocasas merged commit 262ff25 into main Nov 10, 2026
15 checks passed
@gonzalocasas
gonzalocasas deleted the ci/create-github-release branch November 10, 2026 11:01
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.

2 participants