Move twine check to dedicated step #66
Merged
Conversation
This file contains 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
|
Once this is merged I can re-run the libmongocrypt build to complete the publish step. |
ShaneHarvey
approved these changes
Dec 30, 2024
blink1073
added a commit
that referenced
this pull request
Dec 31, 2024
This reverts commit af48d9c.
This was referenced Dec 31, 2024
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.
Because of #62, we are stuck with an older version of twine when using
gh-action-pypi-publish, so use the latest twine to run the check, which supports packaging metadata version 2.4.Addresses failure seen in pymongocrypt release: https://github.com/mongodb/libmongocrypt/actions/runs/12551349971/job/34995728032