Repository navigation
Rebind the coherent release route to 0.113.0 over promoted 0.112.0 (Refs #4640) - #4833
Merged
Merged
Conversation
EHotwagner
force-pushed
the
routine/coherent113-release-route
branch
from
October 23, 2026 11:21
9c20c0d to
51a43c0
Compare
Advance the candidate, feed-readiness and journal selection from the consumed coherent112 route to source 0.113.0 (#4802 Claude Code usage capture) over genuine promoted 0.112.0 (source d5af6a9, content sha256:1a6f0e3a, verified from the release's stable-channel asset), with the fresh prospective journal coord113-claude-usage-20261023-01. Tests bind the new identity and refuse the consumed 112 journal. Source only: no candidate, namespace allocation or publication follows. Refs #4640 Co-Authored-By: Claude Opus 5.5 <[email protected]>
…13.0 release notes f2656d3 (#4812) ships in coherent113 beside the Claude usage capture. Refs #4640 Co-Authored-By: Claude Opus 5.5 <[email protected]>
EHotwagner
force-pushed
the
routine/coherent113-release-route
branch
from
October 23, 2026 11:53
51a43c0 to
5a2333f
Compare
This was referenced Oct 23, 2026
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.
Rebinds the coherent release route from the consumed coherent112 selection to source 0.113.0, which #4802 composed (merge
61526e94, Claude Code transcript usage capture) over the genuine promoted 0.112.0. Without this change the candidate workflow onmainrefuses: it still assertsversion = 0.112.0, whileDirectory.Build.propsdeclares 0.113.0. The journal selection also still names the consumedcoord112-skill-routing-20261021-01.Changes
release-successor-candidate.ymlandrelease-successor-feed-readiness.yml: target 0.113.0, predecessor 0.112.0, tag sourced5af6a98, observationcoherent-0113-absence.release_successor_journal.CURRENT_RELEASE: 0.113.0 over 0.112.0, predecessor sourced5af6a987e915bd0a1b572bcc09ad0d4b2e798b5and contentsha256:1a6f0e3a…59adb. Both were verified from thecoherent-set/v0.112.0stable-channel asset (manifest sha2560c9efdcc…). The fresh prospective journal iscoord113-claude-usage-20261023-01.Rebased 2026-10-23 onto main
c7297c11(#4839 journal CAS re-read, #4837, #4841), then merged with1fac8e92(#4838) inside the coherent113 hold. Main now includes the passive retirement fix (#4835, which ships in 0.113.0) and Host 0.9 source (#4834). The rebase adds one CLI 0.113.0 release-note sentence for the board-v2migration-preparefailure custody (f2656d3, #4812), as the GO review recommended. Release-notes check: 3768 of 35000 characters; fixture 32/32.Not changed: the publisher (
release-successor-publish.py), Host 0.8, published 112 metadata, installed pins, and every original journal or attempt.Scope: source only. No candidate, namespace allocation, main hold or publication follows from this merge. Each of those needs its own admission (fdev).
Local checks at this head: release-successor-candidate 20/20, telemetry-host-published-org-read 14/14, release-successor-recovery 205 (2 skipped), release-successor-journal, release-successor-artifact 24, release-successor-live 44, telemetry-host-successor 28 and new-sdd-workspace-successor 218 all OK. release-successor-authentication shows 24F/22E locally, identical on the
origin/mainbaseline, so it is environment-dependent and not introduced here.Touch-set note: #4831, which edits
scripts/release-successor-publish.py, has merged. The publisher runs from the dispatchedmainSHA, so the candidate and publish runs need a main hold.architecture-map: unaffected
Refs #4640
🤖 Generated with Claude Code