ci(publish): publish via PYPI_USERNAME/PYPI_PASSWORD (legacy auth)#84
Merged
Conversation
Fall back to token/password auth for the PyPI upload so a release can be cut without configuring a Trusted Publisher. Requires PYPI_PASSWORD to be a valid API token (PyPI no longer accepts plain passwords). Re-migrating to OIDC Trusted Publishing is preferred long-term. Signed-off-by: yuriyryabikov <22548029+kurok@users.noreply.github.com>
kurok
added a commit
that referenced
this pull request
Jun 12, 2026
Drop the legacy PYPI_USERNAME/PYPI_PASSWORD auth (from #84): setting an explicit password disables Trusted Publishing AND silently ignores PEP 740 attestations. Use OIDC (no long-lived creds) with attestations: true, alongside the existing build-provenance attestation step. Requires a one-time PyPI Trusted Publisher for namecheap/fast_mail_parser + publish.yml. Also set download-artifact digest-mismatch to warn: the upload@v7/download@v8 pairing can report a spurious digest mismatch that fails artifact collection even though the download succeeds (provenance attestation still covers integrity). Signed-off-by: yuriyryabikov <22548029+kurok@users.noreply.github.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
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.
Switches the PyPI upload step from OIDC Trusted Publishing to the legacy
PYPI_USERNAME/PYPI_PASSWORDsecrets, so v0.4.0 can be released without configuring a Trusted Publisher.PYPI_PASSWORDis a valid API token (withPYPI_USERNAME = __token__) — PyPI no longer accepts plain username/password uploads. If it's a stale 2020 password, the upload will fail with an auth error (no partial upload;skip-existing: truemakes retries safe).Re-migrating to OIDC Trusted Publishing (and deleting these secrets) is the preferred long-term setup.