ci: publish a GitHub Release instead of a bare tag#282
Merged
Conversation
python-deequ historically ships GitHub Releases (v1.1.0..v1.6.0), not bare
tags. Replace the 'git tag + push' step with 'gh release create v${VERSION}
--target ${RELEASE_SHA} --generate-notes', which creates the tag AND the
Release page in one call, pinned to the published commit, after the PyPI
upload. Idempotent (skips if the release already exists).
Note: this change was intended for #281 but landed on that branch after it had
already merged, so it never reached master — hence this follow-up PR.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
kyraman
approved these changes
Jul 9, 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
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
The publish workflow creates a bare git tag on release, but python-deequ historically ships GitHub Releases (v1.1.0…v1.6.0). This switches the post-publish step to create a proper Release.
Change
Replace the
git tag -a v${VERSION} + git pushstep with:— which creates the tag and the Release page (auto-generated notes) in one call, pinned to the exact published commit, after the PyPI upload. Idempotent (skips if the release already exists).
Context
This change was written as part of #281 but was pushed to that branch after #281 had already merged, so it never reached master. This is the follow-up to land it. (The docs/rename portion of #281 did merge and is on master.)
Comment/step change only; no change to publish, versioning, or approval behavior.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.