Describe the bug
The Deploy workflow (.github/workflows/deploy.yaml) was not triggered when the v0.13.0 release was published on 2026-04-11. As a result, the v0.13.0 wheels were not published to PyPI. I manually published them by downloading the release artifacts an running uv publish.
The last successful deploy workflow run was for v0.12.3 on 2026-03-30. There is no deploy run for v0.13.0.
Failing Test
N/A
Expected behavior
Publishing a GitHub release should trigger the deploy workflow via the on: release: types: [published] event, which downloads the release assets and publishes them to PyPI using trusted publishing.
Possible causes
- The release may have been created directly as a published release rather than publishing the existing draft (GitHub does not always fire the
published event in this case).
- A GitHub Actions incident or org-level policy change may have prevented the workflow from running.
Describe the bug
The
Deployworkflow (.github/workflows/deploy.yaml) was not triggered when the v0.13.0 release was published on 2026-04-11. As a result, the v0.13.0 wheels were not published to PyPI. I manually published them by downloading the release artifacts an runninguv publish.The last successful deploy workflow run was for v0.12.3 on 2026-03-30. There is no deploy run for v0.13.0.
Failing Test
N/A
Expected behavior
Publishing a GitHub release should trigger the deploy workflow via the
on: release: types: [published]event, which downloads the release assets and publishes them to PyPI using trusted publishing.Possible causes
publishedevent in this case).