pypa/gh-action-pypi-publish GHSA-5xjx-3w67-w9x9 (critical): versions up to 1.14.2 bundle a certifi trust store that still includes the compromised eMudhra emSign root used in Sigstore checks for Trusted Publishing and attestations. How do I update my PyPI release workflow?

What it is: pypa/gh-action-pypi-publish is the official GitHub Action most Python projects use to upload releases to PyPI, including with Trusted Publishing (OIDC, no API token) and digital attestations. Its Docker image ships Python dependencies, including certifi, the CA trust store that Sigstore and many Python tools use for TLS. After eMudhra's intermediate CA keys were confirmed compromised in October 2026, certifi removed the affected emSign roots, but action releases up to 1.14.2 still bundled the old certifi. The maintainers published this advisory on October 30, 2026 (critical) and fixed it in 1.14.3, which ships without those certificates. The risk is that the publishing step trusts certificates that could be issued by whoever holds the stolen keys, which matters for the integrity of the Sigstore/Trusted Publishing exchange. Am I affected: - Any workflow using pypa/gh-action-pypi-publish at version 1.14.2 or earlier, including the floating release/v1 branch if it hasn't picked up 1.14.3 yet, or a pinned commit SHA from an older release. Search your workflows: grep -rn 'gh-action-pypi-publish' .github/workflows. Fix: 1. Update the action to v1.14.3 or later. If you pin by commit SHA (recommended), update the SHA to the v1.14.3 release commit; if you use release/v1, confirm it now points at 1.14.3 or later. Dependabot's github-actions ecosystem can keep this current. 2. Re-run any release you cut since the eMudhra compromise only if you have reason to doubt it; PyPI shows the attestations and publisher for each file, so compare them with what you expect. 3. Update certifi and the system CA bundle in your other build images and runners too (see the eMudhra trust-store fix): the same stale certificates can sit in any Python environment that hasn't updated certifi since mid-October 2026. Verify: the workflow log shows the action at v1.14.3+, and the release appears on PyPI with the expected Trusted Publisher and attestation. Sources: https://github.com/pypa/gh-action-pypi-publish/security/advisories/GHSA-5xjx-3w67-w9x9 https://github.com/pypa/gh-action-pypi-publish/releases/tag/v1.14.3 https://docs.pypi.org/trusted-publishers/