Repository navigation
Update twine to v7 - #416
Merged
Merged
Conversation
webknjaz
reviewed
Jul 27, 2026
| @@ -1,5 +1,5 @@ | |||
| # | |||
| # This file is autogenerated by pip-compile with Python 3.13 | |||
| # This file is autogenerated by pip-compile with Python 3.14 | |||
Member
There was a problem hiding this comment.
Plz generate the lock file using the same Python runtime as the docker container has.
webknjaz
approved these changes
Jul 28, 2026
webknjaz
left a comment
Member
There was a problem hiding this comment.
Thanks, I think this will get released together with the changes needed for #415 (at least it doesn't look like those blockers are too far away).
cc @facutuesca
Member
Author
|
Thank-you! |
MImmesberger
added a commit
to ttsim-dev/ttsim
that referenced
this pull request
Aug 20, 2026
The `v1.3.0` tag push built fine but failed at the upload gate: ``` Checking dist/ttsim_backend-1.3.0-py3-none-any.whl: ERROR InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version ``` (https://github.com/ttsim-dev/ttsim/actions/runs/32375860674) The workflow installs `build` unpinned, so it picks up a current hatchling, which emits `Metadata-Version: 2.5`. The Twine bundled in `gh-action-pypi-publish@v1.14.0` only knows up to 2.4. `v1.14.2` ships Twine 7, which accepts 2.5 (pypa/gh-action-pypi-publish#416). No repo code caused this — it is floating-dependency drift, which is why 1.2.1 published fine on the identical workflow. **Follow-up needed:** 1.3.0 is still not on PyPI (latest is 1.2.1). Once this merges, the `v1.3.0` tag has to be moved to the fixed commit (or re-created) to re-trigger the publish job. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Merged
2 of 3 tasks
mjbommar
added a commit
to 273v/kaos-web
that referenced
this pull request
Sep 21, 2026
…64) The v0.1.15 publish failed at the upload step: InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version hatchling now emits Metadata-Version: 2.5, and the pinned action was v1.14.1, whose bundled Twine predates 2.5 support. v1.14.2 exists precisely for this -- its release notes call out the Twine v7 bump "to let them upload their sdists and wheels containing core packaging metadata v2.5 to (Test)PyPI" (pypa/gh-action-pypi-publish#416). Local `twine check --strict` did not catch it because `uvx --from twine` resolves current Twine, which accepts 2.5. Only the action's pinned, older copy rejected it, so the gate was green everywhere except the one place that mattered. Nothing was published: PyPI is still at 0.1.14 and the 0.1.15 upload was rejected before any file was accepted. The v0.1.15 tag and its GitHub release (wheel, sdist, SBOM) were created and are untouched. Signed-off-by: Mike Bommarito <michael.bommarito@gmail.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Twine 7.0, which was just released, is required for uploading packages with
Import-Namemetadata, i.e. metadata version 2.5.