Skip to content

fix(ci): pypi-publish workflow — add workflow_dispatch, pin artifacts, handle existing release#102

Merged
nullhack merged 1 commit intomainfrom
fix/pypi-publish-workflow
Apr 22, 2026
Merged

fix(ci): pypi-publish workflow — add workflow_dispatch, pin artifacts, handle existing release#102
nullhack merged 1 commit intomainfrom
fix/pypi-publish-workflow

Conversation

@nullhack
Copy link
Copy Markdown
Owner

Problem

pypi-publish.yml never triggered for v7.0.20260422 because the tag was already on the remote (created by gh release create manually) when tag-release.yml ran — so no push: tags: v* event was emitted.

Changes

  • Add workflow_dispatch with tag input — allows manual re-runs for existing tags
  • Fix release job: if a GitHub Release already exists for the tag, upload dist files to it (gh release upload --clobber) instead of failing on gh release create
  • Pin download-artifact to SHA d3f86a106a0bac45b974a628896c90dbdf5c8093 (v4) — consistent with upload-artifact pin
  • Checkout correct ref in both build and release jobs when triggered via workflow_dispatch

@nullhack nullhack merged commit c0a5c4d into main Apr 22, 2026
5 checks passed
@nullhack nullhack deleted the fix/pypi-publish-workflow branch April 22, 2026 05:45
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.

1 participant