Skip to content

hum: on orchd 0.5 and Orch 0.3 - #108

Merged
adiled merged 1 commit into
mainfrom
orchd-0.5
Nov 12, 2026
Merged

adiled merged 1 commit into
mainfrom
orchd-0.5

Conversation

@adiled

@adiled adiled commented Nov 12, 2026

Copy link
Copy Markdown
Owner

Moves hum onto the latest of both: orchd 0.5.0 and the-orch 0.3.0.

Installer. orchd 0.5 is Zig and ships as GitHub release binaries (it isn't on crates.io), so cargo install orchd --version =0.4.0 could only ever install 0.4. ./install now downloads the pinned v0.5.0 tarball for the host, verifies its .sha256, and installs orchd, orch and the orchd-rootstock-* binaries into ~/.local/bin with atomic renames. orch is required now: orchd 0.5 reads every Orchfile through orch resolve --json. Hosts with no orchd build (only x86_64-linux, aarch64-linux and aarch64-macos have one) get a warning instead of a failed install, since hum itself never calls orchd.

Hives. orchd 0.5 replaced --namespace with --grove and rejects the old flag (error: unexpected argument '--namespace'), so all 14 hive install scripts now grow under --grove "hum-$hive". All 16 hive Orchfiles pass orch validate 0.3.

the-orch 0.3. The only break is that parser::parse_raw is gone. Orch 0.3 takes runtime values as ARG overrides and applies only the ARGs a file declares, so orchfile::resolve now passes the whole environment and no longer pre-scans for declared ARGs. That's the same semantics as before, and the same resolution orchd does. There are 4 new unit tests.

Verified. The installer's orchd step was run in a scratch root against the real release (installs all 5 binaries, version and API checks pass), against a tampered tarball (stops on the checksum mismatch), and against a missing release (stops on the fetch error). Temp dirs are cleaned up in every case. cargo test -p hum passes, including conform.

README mentions of "namespace" (hives/README.md) and the man page's binary list are left for a separate docs change.

orchd 0.5 is Zig and ships as release binaries, not on crates.io, so
the installer's `cargo install orchd =0.4.0` could only ever reach 0.4.
It now fetches the pinned 0.5.0 release for the host, checks its
sha256, and installs orchd with orch and the rootstocks beside it:
orchd reads every Orchfile through `orch resolve --json`, so orch is
no longer optional. A host with no orchd build (Intel macOS) gets a
warning instead of a failed install, since hum never calls orchd.

orchd 0.5 replaced --namespace with --grove and rejects the old flag,
so every bundled hive's install now grows under `--grove hum-<hive>`.

hum parses Orchfiles with the-orch 0.3. Orch 0.3 takes runtime values
as ARG overrides and applies only the declared ones, so the whole
environment goes in and parse_raw, which 0.3 removed, is no longer
needed to find the declared ARGs.
@adiled
adiled merged commit 6989698 into main Nov 12, 2026
13 of 14 checks passed
@adiled
adiled deleted the orchd-0.5 branch November 12, 2026 15:35
adiled added a commit that referenced this pull request Nov 12, 2026
…109)

Brings the READMEs, THRUM.md and the man page in line with #107 (relay peering) and #108 (orchd 0.5, groves, orch beside orchd, iroh-relay: hints).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant