fix(ci): drop the nonexistent twine --trusted-publishing flag - #539
Open
MichaelGHSeg wants to merge 1 commit into
Open
MichaelGHSeg wants to merge 1 commit into
MichaelGHSeg wants to merge 1 commit into
Conversation
twine has no such option, so the upload aborted with exit 2 before contacting PyPI. Trusted publishing needs no flag: twine resolves the password through keyring, then trusted publishing, and defaults the username to __token__ for PyPI, fetching the audience and minting a token over OIDC on its own. --non-interactive so a trusted-publishing failure errors instead of trying to prompt for a password.
This branch has not been deployed
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
1 participant
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 2.4.0 publish failed here:
twine has no such option in any version, so the upload aborted with exit 2 before contacting PyPI. Everything before it succeeded — Artifactory auth, tag/version validation,
uv build.Trusted publishing does not need a flag. twine resolves the password via keyring, then trusted publishing, then a prompt, and defaults the username to
__token__for PyPI; it fetches the audience from/_/oidc/audience, callsdetect_credential, and mints a token at/_/oidc/mint-tokenby itself.--non-interactiveis added so a trusted-publishing failure errors out instead of trying to prompt for a password.Nothing was published, so 2.4.0 is still unused on PyPI. After this merges the tag and release need recreating at the new master so the workflow that runs includes the fix.