Overview
| Comment: | docs(changelog): the public horizon API |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk | feat/horizon-cones |
| Files: | files | file ages | folders |
| SHA3-256: |
76d780fde1524287fe1fa485c70ea8f2 |
| User & Date: | [email protected] on 2026-10-22 14:48:42.000 |
| Other Links: | branch diff | manifest | tags |
Context
|
2026-10-22
| ||
| 15:06 |
Merge branch 'wip/horizon-cursor' into feat/horizon-cones
The horizon cursor (draft-fossil-horizon-00 §6.2.6): an origin that classified a request answers pragma horizon-cursor with its position, a converged client records it per origin and cone and sends it back, and neither side announces again what the other already has. Interoperates with zit both ways. check-in: f704c6d58b user: [email protected] tags: feat/horizon-cones, trunk | |
| 15:06 | Merge branch 'feat/horizon-cones' into wip/horizon-cursor check-in: ec8b4c770b user: [email protected] tags: feat/horizon-cones, trunk | |
| 14:48 | docs(changelog): the public horizon API check-in: 76d780fde1 user: [email protected] tags: feat/horizon-cones, trunk | |
| 14:48 |
test(conformance): skip horizon interop on a zit that predates horizons
TestZitHorizonInterop took whatever zit was on PATH. A zit release from trunk reports the same version as the horizon-rfc build but has no --horizon flag, so the test failed in zit's argument parser. The new zitHorizonBinary probes the binary for horizon support, as zitBinary already probes for send-submanifests, and skips it, or fails the run under REQUIRE_ZIT_BIN=1, with the reason. check-in: 27b85364f2 user: [email protected] tags: feat/horizon-cones, trunk | |
Changes
Modified CHANGELOG.md
from [64ad260d5f]
to [bc10afd1b5].
[diff]