Drop the broken TestPyPI publish job - #36
Merged
Merged
Conversation
The django-pglocks name on TestPyPI is held by an unrelated account, so the trusted-publishing token exchange always fails (invalid-publisher) and the job red-Xed on every tag push. Remove it; build + publish-pypi (on release) remain. Pre-release validation is done locally (uv build + twine check).
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
django-pglocksname on TestPyPI is held by an unrelated account, so the trusted-publishing token exchange always fails (invalid-publisher) and thepublish-testpypijob red-Xed on every tag push. There's no way to claim a name someone else holds, and TestPyPI is only a dry-run.Change
publish-testpypijob frompublish.yml.build+publish-pypi(on a published Release) remain — the real release path is unaffected.Pre-release validation is done locally instead (
uv build+twine check), which is exactly how 2.1.0 was verified before it shipped.