V1 publication must qualify the exact wheel/sdist bytes that are later published.
Required release gate:
- freeze the source commit and require the normal supported Python/OS checks;
- run the real Bitcoin Core v32 integration/fixture checks on the release candidate;
- run optimized/static/differential qualification;
- build wheel and sdist once;
- install those exact artifacts into clean qualification environments;
- record commit, package/tag, dependency/Core versions and SHA256/provenance;
- publish only the same qualified bytes.
Implemented in focused PR #52. The refreshed head 9cf9f44 is mergeable, all review threads are resolved, exact-head Python-package run 645 and Bitcoin Core wallet-fixture run 31 succeeded, and it has a current-head Codex release-gate ACK. The workflow stages qualified artifacts on a draft GitHub release, rechecks hashes/provenance immediately before publication, publishes those same bytes to PyPI, then makes the GitHub release public.
The tag-push publication path cannot execute from the PR itself and still requires the normal release-environment approval on the first real tag. As of 2026-10-03, the official Bitcoin Core 32.0 binary index still publishes only test.rc2/, so #52 correctly remains pinned to the available hash-verified rc2 binary even though a signed rc3 source tag exists.
Keep this issue open until #52 is human-integrated and the final frozen candidate runs the actual release-qualification path.
V1 publication must qualify the exact wheel/sdist bytes that are later published.
Required release gate:
Implemented in focused PR #52. The refreshed head
9cf9f44is mergeable, all review threads are resolved, exact-head Python-package run 645 and Bitcoin Core wallet-fixture run 31 succeeded, and it has a current-head Codex release-gate ACK. The workflow stages qualified artifacts on a draft GitHub release, rechecks hashes/provenance immediately before publication, publishes those same bytes to PyPI, then makes the GitHub release public.The tag-push publication path cannot execute from the PR itself and still requires the normal release-environment approval on the first real tag. As of 2026-10-03, the official Bitcoin Core 32.0 binary index still publishes only
test.rc2/, so #52 correctly remains pinned to the available hash-verified rc2 binary even though a signed rc3 source tag exists.Keep this issue open until #52 is human-integrated and the final frozen candidate runs the actual release-qualification path.