Skip to content

release: ship orchd with its rootstocks as binaries - #74

Merged
adiled merged 3 commits into
mainfrom
release-binaries
Nov 9, 2026
Merged

adiled merged 3 commits into
mainfrom
release-binaries

Conversation

@adiled

@adiled adiled commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

Since #73, bare is a Zig binary that ships beside orchd. A crates.io install can't bring it along, so a release now has to carry binaries.

  • For each target (x86_64-linux, aarch64-linux, aarch64-macos) the job runs just test and just dist, then packs dist/bin as orchd-<target>.tar.gz. On macOS that includes orchd-apple, orchd-osx and orchd-osx-init, signed.
  • A tag publishes the crate as before, then creates the release with the tarballs attached. Both wait on the binaries.
  • Pull requests that touch the workflow or the justfile run the same build, so this one proves itself here. It did, on all three targets.
  • The README's Install section offers a release first and just install from source second.
  • release.sh keeps orchd-rootstock-bare's version in lockstep.

Running on Linux turned up two test-side problems and one real bug:

  • Real bug: a plugin that exits before reading the envelope closed the pipe under orchd's write, and orchd reported "Broken pipe" instead of the plugin's own reason. A closed pipe on that write is now let pass, so the plugin's exit status and stderr carry the reason.
  • Tests: the fake plugin is written under a draft name and copied into place by cp. Otherwise a parallel test's fork can inherit the write fd, and Linux refuses the exec with ETXTBSY.
  • Workflow: the actions now run on Node 24, and fail-fast is off so every target reports.

A release now builds orchd, orchd-rootstock-bare and, on macOS, the Apple
runtimes for x86_64-linux, aarch64-linux and aarch64-macos, tests them, and
attaches one tarball per target. The same build runs on pull requests that
touch the workflow or the justfile.
A test that writes a script and execs it races every fork in the parallel
test process: a sibling's child can inherit the write fd, and Linux refuses
the exec with ETXTBSY. The script is now written under a draft name and
copied into place by cp, so this process never holds it open for writing.
CI runs every target to the end and uses the Node 24 actions.
A plugin may exit before reading the envelope, closing the pipe under
orchd's write. orchd reported the broken pipe instead of the plugin's own
reason. The write now lets a closed pipe pass, so the exit status and stderr
speak. release.sh keeps orchd-rootstock-bare's version in lockstep.
@adiled
adiled merged commit 5dff9b1 into main Nov 9, 2026
5 checks passed
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