Repository navigation
Registry: coord-engine and telemetry-host package-version lag the feeds (0.113.0 / 0.8.0 vs 0.114.3 / 0.9.0); feed check red on main #5216
Description
Parent Outcome: #5097
Work level: Delivery · Track: Active delivery · Intended Status: Done
Owner
Root/fdev assigns the release tooling owner.
Done when
- Registry rows:
registry/dependencies.ymldeclarescoord-engineat the published coherent version (0.114.3,FS.GG.Coord.Clion both feeds) andtelemetry-hostat 0.9.0, with changelog entries and regenerated projections. Thefeedcheck (check-feed-coherence) is then green on main. - Root cause: the coherent release route (0.114.0–0.114.3) published without the registry update step. Either the publisher's post-publication step opens or verifies the registry PR, or the release runbook makes it an explicit gate (Atlas/skill
publishing-and-deployment), so the next coherent release can't leavefeedred. - Required check: decide whether
feedshould become required once green.
Current deliverable
Accepted registry reconciliation PR #5217, merge 79359691b539f60050c70df67954581d44f81e36, with successful main feed readback and Root required-check disposition.
Next action
None within this Delivery. Future release owners apply the merged registry-flip and feed-completion gate.
Blocked on
Nothing.
Activity
EHotwagner commentedon Nov 1, 2026
Root/fdev: owner dispatched (the 0.114.x release owner).
EHotwagner commentedon Nov 2, 2026
Accepted #5216 on 2026-11-02. Registry reconciliation PR #5217 merged as
79359691b539f60050c70df67954581d44f81e36, aligning the published coherent set 0.114.3, Host 0.9.0 and canonical CLI pin, with projections/changelog and release-runbook completion gate. Recorded independent source verdict: Unknown; the native PR has no submitted review. This acceptance relies on the merged source and recorded checks, without inventing a review.The exact merge's main feed workflow succeeded: https://github.com/FS-GG/.github/actions/runs/41350192508. Subsequent main feed runs 41359550007 and 41404030696 also succeeded. This satisfies the requested post-merge feed readback; it is not a freshness assertion for a future candidate, whose release admission must refresh it.
Root decision on the required check: keep the current live-feed push/schedule check advisory. It is path-filtered and external publication can invalidate unrelated PRs, so making it universally required as-is would create false blockers. The merged runbook's owned post-publication registry flip and green-feed completion gate remain mandatory, including before the next candidate. A separately scoped PR-content gate is a possible future improvement, not an unimplemented requirement hidden in this Delivery. No branch-protection changes were made.