fix: remove redundant GitHub release asset upload step - #67
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #67 +/- ##
=======================================
Coverage 82.17% 82.17%
=======================================
Files 48 48
Lines 1419 1419
Branches 110 110
=======================================
Hits 1166 1166
Misses 221 221
Partials 32 32
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
farhan
marked this pull request as draft
August 20, 2026 10:41
python-semantic-release v10.6.x now uploads the built distribution artifacts to the GitHub release directly in the "Run Semantic Release" step (default `upload_to_vcs_release = true`). The separate `publish-action` "Upload to GitHub Release Assets" step then re-uploaded the same filenames, which GitHub rejects with `HTTP 422 already_exists` (see run 32356871133). Drop the redundant `publish-action` step; the main release step handles the GitHub release assets. This regressed on the v10.5.3 -> v10.6.1 bump; it was not present at v1.7.0 which ran on v10.5.3. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
farhan
force-pushed
the
fix-redundant-release-upload
branch
from
August 20, 2026 10:51
b6b6d8c to
cb2f805
Compare
farhan
marked this pull request as ready for review
August 20, 2026 10:52
salman2013
approved these changes
Aug 20, 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
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.
This is a test-run PR so used
fixin the commitThe release run failed at the Upload to GitHub Release Assets step with an
HTTPError: 422 Unprocessable Entitywhile it was uploading thexblocks_extra-1.7.1wheel and sdist to the GitHub release.Root cause
Starting with
v10.6.x,python-semantic-releaseuploads the built distribution to the VCS release by default, becauseupload_to_vcs_releasenow defaults totrue. I was not able to find the exact release note or commit that introduced this change. However, a test PR that downgrades PSR tov10.5.3published successfully without the422, which confirms that the PSR version is the cause.Fix
This PR removes the
publish-actionstep , so that PSR no longer attempts to attach assets to the release. Theupload-artifactstep remains in place, because thepublish_to_pypijob depends on it to publish the wheel and sdist to PyPI via OIDC trusted publishing.Scope of impact
Any repository that has upgraded
python-semantic-releasetov10.6.xand relies on PSR for its release workflow will run into the same422error, so the same fix will need to be applied there as well.🤖 Generated with Claude Code