Repository navigation
Publish DRDID automatically with PyPI Trusted Publishing - #22
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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
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 automatic 1.1.7 upload reached PyPI but failed with HTTP 403 while using the existing username/password secrets. This replaces that authentication with PyPI Trusted Publishing (OIDC), scoped to this repository's
pypi_upload.ymlworkflow andpypienvironment.The publisher keeps the four trusted successful main-push checks and exact tested SHA. It builds without OIDC permission, passes immutable current-run artifacts to a separate publish job, and rechecks CI/main immediately before upload. A main-only manual retry cannot bypass those checks. All releases share one concurrency group.
Before skipping or resuming existing files, it verifies their PyPI digests, wheel/source identities, runtime source, dependency/build metadata, and wheel installation fields. A changed source under an existing version, unsafe archive or yanked file fails clearly; matching partial uploads can finish. Documentation and archive timestamp changes do not require a new release.
Validation: 401 tests plus 92 subtests pass, including all 379 estimator tests and 22 release-gate tests. Actionlint, Python 3.8 syntax, isolated wheel/sdist builds, metadata checks, live read-only exact-SHA GitHub checks and live PyPI preflights pass. All eight runtime Python files are unchanged.
One-time registry configuration must authorize this identity before activation:
drdidd2cml-aiDRDIDpypypi_upload.ymlpypiThe GitHub environment is restricted to
mainand has no per-release reviewer or timer. The four main CI checks remain mandatory with no bypass actors. No estimator, version, dependency pin or numerical tolerance changes. Seedocs/publishing.mdfor setup and operational details.Activation verified: merged as
60b24662e17867eb0ae8a12c0f3ba010639e3e4d; all four main CI checks passed. The exact Trusted Publisher was registered after owner approval. Automatic publisher run published DRDID 1.1.7 without a dispatch or rerun. Both public artifacts pass SHA256, all eight runtime-source files, build-input and metadata verification against merged main and reviewed backend53a6b76.