Repository navigation
Gate v1 publication on final-RC integration and built-artifact verification #5
Description
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.
Activity
BenWestgate commentedon Sep 25, 2026
Bitcoin Core release monitor (2026-09-25): 32.0 is still in RC; the official
bitcoin-core-32.0/index currently contains onlytest.rc2/, and the public download page lists 31.1 as latest stable. Release qualification should therefore treat PR #51's 32.0rc2 run as pre-final evidence, not the final v1 Core qualification. When a newer RC/final appears, repin and rerun before publication.When stable Bitcoin Core 32.0 is released, also clean up BenWestgate/Bails#244: remove the now-dead 32.0rc2 fallback (
VER=32.0rc2/bitcoin-core-32.0/test.rc2) after confirming Bails follows the normal stable-release path.BenWestgate commentedon Sep 27, 2026
Bitcoin Core release monitor refresh (2026-09-26): upstream
bitcoin/bitcoinstill exposesv32.0rc1andv32.0rc2under thev32.0tag namespace, with no finalv32.0tag. Keep #51/#52 pinned to rc2 as pre-final evidence; repin and rerun both the fixture gate and exact-artifact qualification if rc3 or final appears before publication.BenWestgate commentedon Sep 28, 2026
Bitcoin Core release monitor refresh (2026-09-28): upstream still has
v32.0rc2;refs/tags/v32.0rc3and the finalv32.0release are absent. Keep #51/#52 pinned to rc2 as pre-final evidence only. If rc3 or final appears before publication, repin the pinned archive/hash and rerun both the real-Core fixture gate and exact-artifact release qualification.BenWestgate commentedon Oct 1, 2026
Bitcoin Core release monitor refresh (2026-10-01): upstream
bitcoin/bitcoinstill exposes onlyv32.0rc1andv32.0rc2under thev32tag prefix; there is nov32.0rc3or finalv32.0tag. Keep #51/#52 pinned to rc2 as pre-final evidence only. If a newer signed RC or final appears before publication, repin the archive/hash and rerun both the real-Core fixture gate and exact-artifact release qualification.Gate release on exact artifacts