Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
CI: unblock the PyPI publish — Twine 7 pin, plus a manual retry trigger
Louis Choquel94a45682b57a
diff --git a/.github/workflows/publish-pypi.yml b/.github/workflows/publish-pypi.ymlindex 061c84236..f835ac79a 100644--- a/.github/workflows/publish-pypi.yml+++ b/.github/workflows/publish-pypi.yml@@ -6,11 +6,16 @@ on:branches:- main- "pre-release/v*"+ # Manual retry. A publish that fails after the merge (a rejected upload, an+ # expired token) is otherwise unrecoverable: re-running a run replays the+ # workflow file it started with, and the only other trigger is merging a PR+ # into main — which the branch guard restricts to release/vX.Y.Z branches.+ workflow_dispatch:jobs:build:name: Build distribution 📦- if: github.event.pull_request.merged == true+ if: github.event_name == 'workflow_dispatch' || github.event.pull_request.merged == trueruns-on: ubuntu-lateststeps:@@ -38,7 +43,7 @@ jobs:publish-to-pypi:name: >-Publish Python 🐍 distribution 📦 to PyPI- if: github.event.pull_request.merged == true+ if: github.event_name == 'workflow_dispatch' || github.event.pull_request.merged == trueneeds:- buildruns-on: ubuntu-latest@@ -55,12 +60,15 @@ jobs:name: python-package-distributionspath: dist/- name: Publish distribution 📦 to PyPI- uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # release/v1+ # v1.13.0+ bundles Twine 7, which accepts core metadata 2.5. The+ # previous pin did not, so the first v0.43.0 upload was rejected on a+ # wheel hatchling had built correctly.+ uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2github-release:name: >-Create GitHub Release with Changelog- if: github.event.pull_request.merged == true+ if: github.event_name == 'workflow_dispatch' || github.event.pull_request.merged == trueneeds:- build- publish-to-pypi