Repository navigation
Release amap-2026-10-30.1: follow Sandy Codex CLI updates - #4
Merged
Merged
Conversation
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
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.
Release
amap-2026-10-30.1so confirmed adopted unified Codex sandboxes can follow Sandy's automatically updated native CLI builds. The deployment pin is the merged release-line fix proofpoint/amap-deploy-sandy#116; router and connector commits are unchanged.The relay measures the installed build and updates only the controller's operational version under exclusive ownership. The original adoption receipt, retained previous configuration, canonical thread and protected policy binding stay intact. The journal audits the build when the service starts. Host verify accepts only the exact confirmed controller with its version string changed, and still requires current readiness and binding evidence. The pane waits for a current challenge and reports relay holds. Fresh-birth lifecycle rules are unchanged.
The installer and release checker accept numeric date-patch labels, preserving all existing release labels and published tags. The latest installer selects the patch release.
Validation: deployment Python 3.9/3.13 and sibling-canary CI passed; the pinned squash merge has the same tree as the tested head. Fresh exact-component release checks passed, including the pinned build-refresh/adoption/host-verifier mutation suites. All four offline bundles were restored, their commit and tag identities matched the manifest, and Git integrity checks passed. New component tags must match the manifest before promotion. Target-host live protocol compatibility remains a runtime check.