fix: migrate release/verify-install harness from autoconf to autonerves#98
Merged
Merged
Conversation
The autoconf→autonerves package rename was not propagated to the release-fidelity / verify-install harness, so Stage-3 tried to `pip install autoconf==<today's dev>` from TestPyPI — which only publishes `autonerves` now — breaking nightly-release and workspace-validation with 'No matching distribution found for autoconf'. Migrate the current-build install lists, import checks, the Colab setup_colab bootstrap, DEFAULT_PACKAGES and the test expectation to `autonerves`. The Check A/E historical-pin block (2026.2.26.4, a yanked release predating the rename) intentionally keeps `autoconf`, and the docs-build/lib-tests case statements keep accepting `autoconf` as an input alias for repo=PyAutoNerves. Fixes #97 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
What
Migrate PyAutoHeart's release-fidelity / verify-install harness from the old
autoconfpackage name toautonerves.Why
The
autoconf → autonervesrename (PyAutoConf → PyAutoNerves) was merged into the libraries on 2026-07-19/20 but not propagated here. The nightly now publishes theautonerveswheel, but Stage-3 still didpip install autoconf==<today's dev>from TestPyPI:This broke both
nightly-release(Stage 3, run 29719984654) andworkspace-validationovernight 2026-07-20.Changes (6 files, 1:1 migration)
heart/checks/verify_install.sh— current-build install list (Check C/F$TARGET_VERSION), import checks (B/D), Colabsetup_colabbootstrap..github/workflows/workspace-validation.yml—autoconf[optional]→autonerves[optional].heart/checks/import_time.py—DEFAULT_PACKAGES.tests/test_validate.py— package-list expectation (39 passed)..github/workflows/{docs-build,lib-tests}.yml— cosmetic help text.Deliberately preserved
autoconf==2026.2.26.4) — a yanked release predating the rename; only exists asautoconf.autoconfas an input alias mapping torepo=PyAutoNerves.Validation
bash -nclean;pytest tests/test_validate.py→ 39 passed. On merge, the nextnightly-releaseStage 3 andworkspace-validationshould resolve theautonerveswheels and go green.Fixes #97