feat: backfill GitHub releases and emit release on publish#119
Merged
Conversation
Add scripts/backfill-releases.sh to create GitHub releases for the already-published PyPI versions (0.1.0, 0.2.0), downloading wheel and sdist artifacts from PyPI and attaching them to the corresponding tags. Update .github/workflows/publish.yml to create a GitHub release on every future tag push: upgrades the job's `contents` permission from read to write and adds a `gh release create` step after the PyPI publish step, attaching the built artifacts from sdk/dist/. Closes #6
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Summary
scripts/backfill-releases.sh: a one-shot script that downloads wheel and sdist artifacts for the already-published PyPI versions (0.1.0, 0.2.0) from the PyPI JSON API and creates GitHub releases on the corresponding tags (v0.1.0,v0.2.0) with--generate-notesand attached artifacts..github/workflows/publish.yml: upgrade thepublishjob'scontentspermission fromreadtowriteand add agh release createstep after the PyPI publish step, attaching the built artifacts fromsdk/dist/so every future tag push produces a GitHub release automatically.Test plan
scripts/backfill-releases.shmanually (requiresghauth as a repo admin) and confirm GitHub releases appear forv0.1.0andv0.2.0with.whland.tar.gzattached.Closes #6
🤖 Generated with Claude Code