ci: create GitHub Release after PyPI publish#555
Merged
Conversation
Restores tag + GitHub Release creation that was previously handled by the Speakeasy reusable workflow. Tag scheme matches what Speakeasy used (v<version>). Release body is built from the latest entry in RELEASES.md so the format matches v1.x / v2.x releases through v2.4.5. PyPI publishing is atomic (no staging), so the release is created after gh-action-pypi-publish succeeds. Adds contents: write to the workflow permissions, required by gh release create.
louis-sanna-dev
approved these changes
May 27, 2026
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
3 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.
The Speakeasy reusable workflow used to create a git tag and GitHub Release for every published version. That stopped when we switched to publishing to PyPI directly with
pypa/gh-action-pypi-publish, leavingv2.4.7untagged.This adds a
Create GitHub Releasestep after the publish step. Tag scheme matches what Speakeasy used (v<version>); release body is built from the latest entry inRELEASES.mdso the format matches earlier releases.contents: writeis added to the workflow permissions, required bygh release create.PyPI publishing is atomic so there is no orphan-tag risk.
v2.4.7will be backfilled separately.