|
| 1 | +--- |
| 2 | +title: "Farrow 0.2.0: selected convergence and release integrity" |
| 3 | +linkTitle: Farrow 0.2.0 |
| 4 | +description: VPN-aware network preflight, truly selected scale-out, committed-state integrations, signed multi-platform artifacts, and the 0.1.0 upgrade boundary. |
| 5 | +date: 2026-09-01 |
| 6 | +weight: 1 |
| 7 | +categories: [Release] |
| 8 | +tags: [Farrow 0.2.0, QEMU, macOS, Linux, Release, Supply Chain] |
| 9 | +icon: fa-solid fa-rocket |
| 10 | +--- |
| 11 | + |
| 12 | +Farrow 0.2.0 is the current public pre-1.0 release. It keeps the Pigsty |
| 13 | +inventory and on-disk deployment format introduced by 0.1.0 while fixing the |
| 14 | +network and selected-convergence boundaries found during the final native |
| 15 | +replay. |
| 16 | + |
| 17 | +## What changed |
| 18 | + |
| 19 | +- A less-specific VPN exclusion such as `10.0.0.0/8` no longer blocks |
| 20 | + Farrow's owned `10.10.10.0/24`; equal or more-specific foreign routes, |
| 21 | + overlapping interfaces, occupied addresses, and a missing owned route still |
| 22 | + fail closed. |
| 23 | +- `farrow up <node>` downloads and prepares only the selected node. Desired |
| 24 | + inventory peers without state appear as `absent`; SSH/hosts/provisioning, |
| 25 | + UUID and port allocation, lifecycle commands, and persistent-disk checks use |
| 26 | + the committed node set without losing future scale-out intent. |
| 27 | +- New guests write `# farrow-deployment-host` and remove both that marker and |
| 28 | + the released `# farrow-project-host` marker before adding current host rows. |
| 29 | +- Command cancellation, structured output, confirmation, `reload`, diagnostic |
| 30 | + redaction, installer retention, and the smaller dependency graph from the |
| 31 | + unpublished intermediate work are included directly in 0.2.0. |
| 32 | + |
| 33 | +## Native and release evidence |
| 34 | + |
| 35 | +The exact source commit completed a macOS arm64/HVF replay with MonoProxy |
| 36 | +active: selected `u24-1` create/SSH/stop/start, incremental cached `el9-1` |
| 37 | +create, two-node SSH, five explicit absent peers, and whole destroy all passed. |
| 38 | +On Ubuntu 26.04 amd64/KVM, the current Linux binary audited an existing |
| 39 | +four-node deployment and reached its control guest without mutation. |
| 40 | + |
| 41 | +Local `make check`, source CI, and the complete packaging workflow passed. The |
| 42 | +tag workflow built four archives, amd64/arm64 DEB and RPM packages, SPDX SBOMs, |
| 43 | +Homebrew formula, installer, checksums, and release metadata. GitHub Actions |
| 44 | +publishes those verified CI outputs without a separate application signature |
| 45 | +or provenance bundle. |
| 46 | + |
| 47 | +The signed image Catalog remains revision `2026082903` with 9 families and 27 |
| 48 | +architecture artifacts. The default repository remains |
| 49 | +`https://repo.pigsty.cc/farrow`; `repo.pgsty.com/farrow` is an independently |
| 50 | +verified source/alternate endpoint, not the compiled default. |
| 51 | + |
| 52 | +## Install or upgrade |
| 53 | + |
| 54 | +Download `install.sh` and the assets from the |
| 55 | +[Farrow 0.2.0 GitHub Release](https://github.com/pgsty/farrow/releases/tag/v0.2.0): |
| 56 | + |
| 57 | +```bash |
| 58 | +chmod +x install.sh |
| 59 | +FARROW_VERSION=0.2.0 ./install.sh |
| 60 | +farrow version |
| 61 | +farrow doctor |
| 62 | +``` |
| 63 | + |
| 64 | +0.1.0 deployment state remains readable. Run `farrow status` while retained |
| 65 | +VMs are live to converge any pre-release process-birth identity. Existing |
| 66 | +guests adopt the new `/etc/hosts` marker when recreated. |
| 67 | + |
| 68 | +Because Farrow is still below 1.0, GitHub labels 0.2.0 as a pre-release even |
| 69 | +though it is the published current release. |
0 commit comments