Skip to content

fix: remove redundant GitHub release asset upload step - #67

Merged
farhan merged 1 commit into
mainfrom
fix-redundant-release-upload
Aug 20, 2026
Merged

fix: remove redundant GitHub release asset upload step#67
farhan merged 1 commit into
mainfrom
fix-redundant-release-upload

Conversation

@farhan

@farhan farhan commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

This is a test-run PR so used fix in the commit

The release run failed at the Upload to GitHub Release Assets step with an HTTPError: 422 Unprocessable Entity while it was uploading the xblocks_extra-1.7.1 wheel and sdist to the GitHub release.

Root cause

Starting with v10.6.x, python-semantic-release uploads the built distribution to the VCS release by default, because upload_to_vcs_release now defaults to true. I was not able to find the exact release note or commit that introduced this change. However, a test PR that downgrades PSR to v10.5.3 published successfully without the 422, which confirms that the PSR version is the cause.

Fix

This PR removes the publish-action step , so that PSR no longer attempts to attach assets to the release. The upload-artifact step remains in place, because the publish_to_pypi job 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-release to v10.6.x and relies on PSR for its release workflow will run into the same 422 error, so the same fix will need to be applied there as well.

🤖 Generated with Claude Code

@codecov

codecov Bot commented Aug 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.17%. Comparing base (798088e) to head (cb2f805).

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           
Flag Coverage Δ
unittests 82.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@farhan
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
farhan force-pushed the fix-redundant-release-upload branch from b6b6d8c to cb2f805 Compare August 20, 2026 10:51
@farhan
farhan marked this pull request as ready for review August 20, 2026 10:52
@farhan
farhan merged commit 3a9f71e into main Aug 20, 2026
8 checks passed
@farhan
farhan deleted the fix-redundant-release-upload branch August 20, 2026 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants