Create a GitHub release for each published version - #4
Merged
Merged
Conversation
Adds CHANGELOG.md; the publish workflow now creates release v<version> with the matching changelog section and the built wheel/sdist attached. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Koo8a1vU5D6JttUkzjxE6H
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
2 participants
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.
Summary
CHANGELOG.mdwith the 2.0.0 notes.publish.ymlgets areleasejob. After the PyPI publish step, it creates the GitHub releasev<version>:CHANGELOG.mdchanges.Merging this creates the v2.0.0 release. Because 2.0.0 is already on PyPI, the publish step skips it.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Koo8a1vU5D6JttUkzjxE6H
Generated by Claude Code