https://barn.pgsty.com/tags/farrow-0.2.0/ Recent content in Farrow 0.2.0 on Barn Hugo en-US Tue, 01 Sep 2026 00:00:00 +0800 https://barn.pgsty.com/blog/release/farrow-0.2.0/ Tue, 01 Sep 2026 00:00:00 +0800 https://barn.pgsty.com/blog/release/farrow-0.2.0/ <p>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.</p> <h2 id="what-changed">What changed </h2> <ul> <li>A less-specific VPN exclusion such as <code>10.0.0.0/8</code> no longer blocks Farrow&rsquo;s owned <code>10.10.10.0/24</code>; equal or more-specific foreign routes, overlapping interfaces, occupied addresses, and a missing owned route still fail closed.</li> <li><code>farrow up &lt;node&gt;</code> downloads and prepares only the selected node. Desired inventory peers without state appear as <code>absent</code>; SSH/hosts/provisioning, UUID and port allocation, lifecycle commands, and persistent-disk checks use the committed node set without losing future scale-out intent.</li> <li>New guests write <code># farrow-deployment-host</code> and remove both that marker and the released <code># farrow-project-host</code> marker before adding current host rows.</li> <li>Command cancellation, structured output, confirmation, <code>reload</code>, diagnostic redaction, installer retention, and the smaller dependency graph from the unpublished intermediate work are included directly in 0.2.0.</li> </ul> <h2 id="native-and-release-evidence">Native and release evidence </h2> <p>The exact source commit completed a macOS arm64/HVF replay with MonoProxy active: selected <code>u24-1</code> create/SSH/stop/start, incremental cached <code>el9-1</code> 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.</p>