Commit 49216e6
ci: publish threadplane-middleware with uv, ending the twine metadata skew
The real-release path used the pinned pypa/gh-action-pypi-publish image,
whose bundled twine rejects the Metadata-Version 2.5 that current uv build
emits: 'InvalidDistribution: 2.5 is not a valid metadata version'. The
dry-run path already used uv publish and passed — the two paths disagreed
about the artifact between them. Observed on the first real 0.0.2 publish
attempt (dry-run green, real release red, nothing uploaded).
Build, dry-run, and publish now share one toolchain. PyPI trusted
publishing binds to repo + workflow filename, not the action, so the same
OIDC grant works; uv consumes it via --trusted-publishing always.
Trade-off, stated: the pypa action also uploaded PEP 740 attestations.
uv publish does not yet; losing them is acceptable against a publish path
that cannot ship at all.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent 2414766 commit 49216e6
1 file changed
Lines changed: 9 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
76 | 76 | | |
77 | 77 | | |
78 | 78 | | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
79 | 86 | | |
80 | 87 | | |
81 | | - | |
82 | | - | |
83 | | - | |
84 | | - | |
| 88 | + | |
| 89 | + | |
0 commit comments