Supply Chain on Barn

Farrow 0.5.0: explicit disposal, explicit repositories, reproducible images

Thu, 03 Sep 2026 00:00:00 +0800

Note

This page describes 0.5.0. Official mirror failover was added in 0.7.0, and the unreleased 0.9 candidate removes the rm alias. Use current CLI guidance for your installed version.

Farrow 0.5.0 was the public pre-1.0 release superseded by 0.6.0. It adds an explicit command for disposable labs, makes repository geography an operator choice, and adds a reproducible path for preparing the next official guest images. The Pigsty Inventory contract, deployment state format, and embedded Catalog revision 2026082903 are unchanged.

Farrow 0.2.0: selected convergence and release integrity

Tue, 01 Sep 2026 00:00:00 +0800

Farrow 0.2.0 was the public pre-1.0 release superseded by 0.3.0. It keeps the Pigsty inventory and on-disk deployment format introduced by 0.1.0 while fixing the network and selected-convergence boundaries found during the final native replay.

What changed

A less-specific VPN exclusion such as 10.0.0.0/8 no longer blocks Farrow’s owned 10.10.10.0/24; equal or more-specific foreign routes, overlapping interfaces, occupied addresses, and a missing owned route still fail closed.
farrow up <node> downloads and prepares only the selected node. Desired inventory peers without state appear as absent; SSH/hosts/provisioning, UUID and port allocation, lifecycle commands, and persistent-disk checks use the committed node set without losing future scale-out intent.
New guests write # farrow-deployment-host and remove both that marker and the released # farrow-project-host marker before adding current host rows.
Command cancellation, structured output, confirmation, reload, diagnostic redaction, installer retention, and the smaller dependency graph from the unpublished intermediate work are included directly in 0.2.0.

Native and release evidence

The exact source commit completed a macOS arm64/HVF replay with MonoProxy active: selected u24-1 create/SSH/stop/start, incremental cached el9-1 create, two-node SSH, five explicit absent peers, and whole destroy all passed. On Ubuntu 26.04 amd64/KVM, the current Linux binary audited an existing four-node deployment and reached its control guest without mutation.

repo.yaml Is Intent; catalog.json Is Evidence

Sat, 29 Aug 2026 19:00:00 +0800

Note

Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for released versus candidate behavior and dated acceptance evidence.

A static image repository sounds like a directory of qcow2 files plus a JSON index. The difficult part is deciding which facts a maintainer may write by hand and which facts must be derived from the bytes being published.