Repository navigation
ci(release): pin pypi-publish to v1.14.3 - #5
Merged
Merged
Conversation
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.
The v0.1.1 release run failed at the PyPI upload: https://github.com/e2b-dev/e2b-adk-plugin/actions/runs/39931590130. The pinned
pypa/gh-action-pypi-publishcommit bundles Twine 6.1.0, which rejects theMetadata-Version: 2.5that current hatchling writes (InvalidDistribution: '2.5' is not a valid metadata version). The build job passed because it already uses the locked Twine 7.0.0 from #4.This moves the action to v1.14.3 (
7245906), which bundles Twine 7.0.0. v1.14.3 is also the pypi-publish version the eMudhra intermediate-CA disclosure lists as patched: https://emudhra.we-have-a-problem.com/.After merge, v0.1.1 gets re-cut on the new commit. Nothing reached PyPI, which still shows 0.1.0.