release: coordinate the Python 3.12 core floor

[Jammy2211]

Overview

Coordinate the five-package core release that publishes the already-merged Python 3.12 floor in dependency order. This phase does not add source changes: it locks exact main SHAs, records the pre-floor fallback releases, runs the release rehearsal/integration gates after authorization, and verifies the published metadata on both sides of the floor.

Manual release execution is human-required. TestPyPI/PyPI uploads, tags, and the final release will not be dispatched until the human chooses the version and explicitly authorizes this release.

Plan

• Record the current unyanked PyPI releases that Python 3.11 can continue to resolve.
• Lock and verify clean synchronized main SHAs for PyAutoNerves, PyAutoArray, PyAutoFit, PyAutoGalaxy, and PyAutoLens.
• Obtain the human version choice and explicit authorization for the coordinated manual release.
• After authorization, run the full Stage 0-3 release validation: preflight, unit evidence, TestPyPI rehearsal, exact-wheel workspace integration, ingest, and Heart verdict.
• Require Heart GREEN for release; do not carry the development YELLOW acknowledgement into a release.
• Delegate packaging/tagging/publication to the Build/Hands release path in dependency order.
• Verify published wheels install on Python 3.12/3.13, reject the new exact release on 3.11, and preserve the recorded older unyanked fallback. Do not yank usable historical wheels.

Detailed release plan

Current PyPI fallback census (2026-07-29)

Distribution	Last compatible unyanked release	Current Requires-Python
autoconf	2026.7.15.1	>=3.9
autoarray	2026.7.29.1	>=3.9
autofit	2026.7.29.1	>=3.9
autogalaxy	2026.7.29.1	>=3.9
autolens	2026.7.29.1	>=3.9

These versions remain usable Python 3.11 fallback candidates after newer releases declare >=3.12.

Exact source heads

Repository	Main SHA	State
PyAutoNerves	a9bf45612ecdf53abb586def7e5635ac7d84872d	clean, equals origin/main
PyAutoArray	41c55a44f50ad3966591dd6317c59dd55beac7ba	clean, equals origin/main
PyAutoFit	241f2d69c4d8d0d1df19765431caacfcc3468da9	clean, equals origin/main
PyAutoGalaxy	b9d9927fae6b8b3359764f51c512fc2852a78793	clean, equals origin/main
PyAutoLens	b40fb0ba6281eb868151f76226f5420a08ba44e7	clean, equals origin/main

Affected repositories

• PyAutoHands (primary release executor)
• PyAutoHeart (release validation and verdict)
• PyAutoNerves
• PyAutoArray
• PyAutoFit
• PyAutoGalaxy
• PyAutoLens

Branch survey

This is a release of already-merged code. No feature branch is proposed; every package must be built from the exact clean main heads above.

Implementation and validation steps

1. Refresh Heart and run the Release Agent Stage 0/1 preflight without dispatch.
2. Ask for the coordinated version/minor choice and explicit release authorization.
3. Only after that authorization, dispatch the TestPyPI rehearsal and capture exact artifacts and commit SHAs.
4. Dispatch Heart release-mode workspace validation against the exact TestPyPI version.
5. Ingest rehearsal and integration artifacts; require a fresh Heart GREEN verdict.
6. Invoke the Build release door with the chosen version. No force on YELLOW or RED.
7. Check PyPI JSON/wheel metadata, supported installs, below-floor rejection, and Python 3.11 fallback behavior.
8. Record results in PyAutoMind and this issue. Issue closure remains a separate human action.

Key files and workflows

• PyAutoHands .github/workflows/release.yml
• PyAutoHands pre_build.sh
• PyAutoHeart .github/workflows/workspace-validation.yml
• PyAutoHeart heart/checks/verify_install.sh
• PyAutoBrain release validate / release door

Original Prompt

Click to expand starting prompt

Python 3.12 floor — Phase 3: coordinated core release

Recheck PyPI last-compatible unyanked versions, obtain the human version choice, pass fresh Heart/pre-build gates, and release PyAutoNerves, PyAutoArray, PyAutoFit, PyAutoGalaxy, and PyAutoLens coherently. Verify the published wheels reject Python 3.11 and install on 3.12/3.13. Do not yank usable historical wheels. Record every unyanked pre-floor fallback that pip can still select so Phase 6 describes rollback behavior accurately rather than promising a hard resolution error.

[Jammy2211]

Phase 3 preflight checkpoint

Completed without dispatching or uploading anything:

• All five core repositories are clean main and exactly match origin/main at the SHAs recorded in the issue.
• Release Agent Stage 0/1 preflight returned ok=true.
• Current CI conclusions were reported as unknown/in-progress warnings, not failures; these must resolve before promotion.
• PyPI fallback census is recorded: autoconf 2026.7.15.1 and the other four core distributions 2026.7.29.1 are unyanked and still support Python 3.11.
• Four distributions already use the 2026.7.29.1 date release, so the recommended coherent release choice is minor 2, yielding 2026.7.29.2 across all five.

Human-required decision

Please choose one:

1. Reply "2, rehearsal only" to authorize the TestPyPI rehearsal and Stage 3 release-integration validation, then stop before live PyPI publication.
2. Reply "2, authorize release on unchanged YELLOW" to authorize the rehearsal plus live coordinated release if all exact-source checks pass, no RED appears, and Heart is either GREEN or remains exactly the acknowledged YELLOW 65 four-reason set. Any changed reason set stops.
3. Provide a different minor/version or constraints.

No TestPyPI/PyPI upload, tag, release workflow dispatch, force-on-YELLOW, yank, or issue closure will occur until this is answered.

[Jammy2211]

Human release authorization received in the live session:

"2, authorize release on unchanged YELLOW — authorize the complete release if validation passes and Heart reason set remains exactly unchanged."

Bound decision:

• Minor: 2
• Coordinated version: 2026.7.29.2
• Authorized: TestPyPI rehearsal, Stage 3 release integration, and live five-package release if every gate passes.
• Heart allowance: GREEN, or exactly YELLOW 65 with these four reasons and no additions/changes:
  1. workspace validation not passing (13 failed, 2026-07-21T19-05-22Z)
  2. 33 stale parked script(s)
  3. manifest drift: tenant firewall (organ code) — 6 mismatch(es) vs PyAutoMind/repos.yaml
  4. release validation stale: source moved since rehearsal (PyAutoNerves, PyAutoFit, PyAutoArray, PyAutoGalaxy, PyAutoLens)

Any RED, changed reason text/set, source SHA drift, failed check, or version mismatch stops before publication. No yanks or issue closures are authorized.

[Jammy2211]

Stage 3 release-validation checkpoint — STOP before live publication

TestPyPI rehearsal passed for all five packages:

• Version: 2026.7.29.2.dev68901
• Run: https://github.com/PyAutoLabs/PyAutoHands/actions/runs/30455540795

Release integration completed against the exact recorded source SHAs:

• Run: https://github.com/PyAutoLabs/PyAutoHeart/actions/runs/30456078786
• Workspace report: READY, 588 passed / 0 failed / 91 deliberately skipped
• Install A/B/C/D/F: PASS
• Python 3.12 exact install/import: PASS
• Python 3.13 exact install/import: PASS
• Python 3.11 exact-version Requires-Python rejection: PASS
• Install E historical yanked-pin check: FAIL

Check E failure locus:

• Today floor-verification commit added setup-python in order 3.11, 3.12, 3.13, so unqualified python3 was 3.13.
• Check E still creates its legacy 2026.2.26.4 environment with unqualified python3.
• That historical stack caps NumPy at 2.0.1 and SciPy at 1.14.0. On Python 3.13 pip found no compatible wheel, attempted a SciPy source build, and failed because OpenBLAS was unavailable.
• A focused diagnostic run of the same Check E on Python 3.12 passed with all five historical packages installed at 2026.2.26.4, confirming a Heart test-harness Python-selection defect rather than a rehearsed-wheel failure.

The final stage report is integrate:fail. After canonical ingestion Heart is RED with two new reasons:

1. install verification FAILED (testpypi; checks E)
2. release validation FAILED (stage integrate)

The unchanged-YELLOW authorization condition is therefore not met. No live PyPI release workflow, tag, yank, or issue closure was dispatched. PyAutoMind checkpoint: 6ede7d9.

[Jammy2211]

Stage 3 validation passed — live release remains held

The corrective PyAutoHeart change is merged unchanged and the definitive validation has passed:

• PyAutoHeart PR: fix: pin legacy release check to Python 3.12 PyAutoHeart#117
• Merged commit: bda57c16a16763604967a1e1e4ed11ced22d516e
• Reviewed head: 8259dcfb3fc7b401e4405473c3ddcf2b99e0610a (merged tree identical)
• TestPyPI rehearsal: https://github.com/PyAutoLabs/PyAutoHands/actions/runs/30455540795
• Definitive integration: https://github.com/PyAutoLabs/PyAutoHeart/actions/runs/30472573498
• Version under validation: 2026.7.29.2.dev68901
• Source SHAs: unchanged exact five-library set recorded in this issue
• Integration totals: 588 passed / 0 failed / 91 intentionally skipped / 0 timeouts
• Install verification: A-F all PASS; 3.12 and 3.13 supported, 3.11 rejected, historical Check E PASS on 3.12
• Heart release validation: rehearsal PASS, integration PASS, release_ready: true

Authoritative Heart verdict is now YELLOW 80 with exactly:

1. workspace validation not passing (13 failed, 2026-07-21T19-05-22Z)
2. 33 stale parked script(s)
3. manifest drift: tenant firewall (organ code) — 6 mismatch(es) vs PyAutoMind/repos.yaml

The prior human authorization was bound to an exact four-reason YELLOW 65 set. Its fourth reason—release validation stale: source moved since rehearsal (...)—has cleared, so the current reason set is different. The recorded condition said any changed reason set stops. Accordingly, no live PyPI workflow, tag, yank, announcement, or issue closure was dispatched.

The release review is held at the Heart decision gate. Source development is unblocked: the corrective task claim/worktree/branches are cleaned and PyAutoHeart main is current.

[Jammy2211]

Fresh live-release authorization — 2026-07-29

The human explicitly resumed the remaining release checkpoint in chat with: “continue and go then”, and instructed that Claude no longer be delegated to.

This authorization is bound to minor version 2 and exactly this current Heart YELLOW reason set:

1. workspace validation not passing (13 failed, 2026-07-21T19-05-22Z)
2. 33 stale parked script(s)

There are no RED or stale reasons. The prior tenant-firewall manifest reason is cleared.

The validated five-library source set is byte-for-byte unchanged on GitHub main:

• PyAutoNerves a9bf45612ecdf53abb586def7e5635ac7d84872d
• PyAutoFit 241f2d69c4d8d0d1df19765431caacfcc3468da9
• PyAutoArray 41c55a44f50ad3966591dd6317c59dd55beac7ba
• PyAutoGalaxy b9d9927fae6b8b3359764f51c512fc2852a78793
• PyAutoLens b40fb0ba6281eb868151f76226f5420a08ba44e7

Existing release-fidelity evidence remains applicable: TestPyPI 2026.7.29.2.dev68901; Stage 3 588 passed / 0 failed / 91 skipped / 0 timeouts; install checks A–F all PASS, including Python 3.12/3.13 support and Python 3.11 rejection.

Authorized action: invoke the manual release door with --force for this exact YELLOW set and minor version 2. Stop if the reasons or validated library SHAs change. No issue closure is authorized.

[Jammy2211]

Live release outcome for Python >=3.12 migration

• Run: https://github.com/PyAutoLabs/PyAutoHands/actions/runs/30487799523
• Version: 2026.7.29.2
• Mode: live
• Published successfully to PyPI: autonerves, autofit, autoarray, autogalaxy, autolens
• PyPI metadata verified for all five: Requires-Python >=3.12, two artifacts each, none yanked
• Job summary: 31 success, 5 failure, 1 skipped
• Heart after the run: YELLOW 80 with the exact authorized reason set unchanged:
  • workspace validation not passing (13 failed, 2026-07-21T19-05-22Z)
  • 33 stale parked script(s)

Failure classification:

1. autogalaxy_workspace smoke: one known workspace-class failure in interferometer/start_here.py at nufftax autodiff, ValueError: too many values to unpack; all other scripts in that smoke job passed.
2. autofit_assistant and autolens_assistant wiki-currency workflows still selected Python 3.11, so pip correctly rejected the new >=3.12 distributions.
3. The two wiki-drift issue jobs then failed because the preceding wiki jobs produced no report artifacts.

Separate release-hygiene incident:

• pre_build commit 95f7502 accidentally committed the top-level =3.12 file and run_logs/ in PyAutoHands.
• No release workflow or source files were included in that accidental scope; history will not be rewritten.
• This needs a narrow follow-up cleanup and staging guard.

No issue is being closed by this update.