Skip to content

Revert "Switch GitHub release step to use 'gh release create'" #338

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
colindean merged 1 commit into from
Mar 29, 2026
Merged

Revert "Switch GitHub release step to use 'gh release create'" #338

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions .github/workflows/build_wheels.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,12 +127,13 @@
output: generated_changelog.md

- name: Create GitHub release
# TODO: handle situation where the GH Release already exists so we don't overwrite good release notes
run: |
TAG="${GITHUB_REF//refs\/tags\/}"
gh release create ${TAG} \
--notes-file generated_changelog.md
dist/**/*
uses: softprops/action-gh-release@153bb8e04406b158c6c84fc1615b65b24149a1fe # v2.6.1

Check notice

Code scanning / zizmor

action functionality is already included by the runner Note

action functionality is already included by the runner
with:
body_path: generated_changelog.md
files: dist/**/*
# In case the release already exists because it was manually created,
# and the author has written a SMASHINGLY GOOD blurb.
append_body: true

# Test PyPI
test_pypi_publish:
Expand Down
Loading