Repository navigation
Prepare 0.23.1 with recoverable setup and tested release assets - #13
Conversation
antono3
left a comment
There was a problem hiding this comment.
Agent code review of 1454090.
Reviewed manifest/declaration agreement, immutable compiler/bootstrap pins, workflow checkout paths and profile selection, installed-tag verification, bounded read-only diagnostics and failure-oriented regression fixtures. Existing compiler/dependency versions and advisory lanes are preserved. No blocking findings. Reviewed transactional staging, atomic cache commit, scoped cleanup and preservation of working/user-modified caches. Local Windows recovery fixtures passed. Reviewed version-derived archives, release source/CI gating, checksum/manifest preparation and ABI-validated native caching. Publication must use the exact tested archives and passing draft-download consumers.
All 8 applicable PR checks and complete latest-head workflows passed. This is agent review, not independent human approval.
Torus releases currently require manual assembly, CI uses fixed 0.23.0 archive names, and interrupted setup can leave an unusable cache. Prepare 0.23.1 with version-derived archive names, transactional tool/check-out preparation, failure-recovery fixtures, and read-only diagnostics.
Add a release collector that requires successful main CI for the exact clean source commit, downloads the tested Windows/Linux archives, and creates checksums, a compatibility/source manifest and release notes. Document draft-download testing before publication. Preserve the prior release and its assets.
Cache native vcpkg binaries by ports commit and compatibility pins while retaining ABI validation and installation of requested triplets.
Validation: local Windows recovery fixtures and all 15 Python regression tests passed; workflow actionlint and whitespace checks passed. Full CI is required before review and merge. Draft and published release consumers will validate the final downloads.