<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Catalog on Barn</title>
    <link>https://barn.pgsty.com/tags/catalog/</link>
    <description>Recent content in Catalog on Barn</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0800</lastBuildDate>
    
    
      <atom:link href="https://barn.pgsty.com/tags/catalog/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Farrow 0.3.0: explicit catalogs and actionable readiness</title>
        <link>https://barn.pgsty.com/blog/release/farrow-0.3.0/</link>
        <pubDate>Wed, 02 Sep 2026 00:00:00 +0800</pubDate>
        
        <guid>https://barn.pgsty.com/blog/release/farrow-0.3.0/</guid>
        <description>&lt;p&gt;Farrow 0.3.0 was the public pre-1.0 release superseded by 0.4.0. It removes implicit&#xA;Catalog refreshes, turns guest bootstrap failures into actionable per-node&#xA;results, and simplifies the CLI without changing the Pigsty Inventory or&#xA;fixed-IP deployment model.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-changed&#34;&gt;What changed&#xA;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;up&lt;/code&gt;, &lt;code&gt;plan&lt;/code&gt;, and ordinary &lt;code&gt;image&lt;/code&gt; commands use one active local Catalog&#xA;snapshot and never fetch Catalog metadata implicitly. &lt;code&gt;farrow update&lt;/code&gt;&#xA;explicitly fetches the configured repository; &lt;code&gt;image sync&lt;/code&gt; activates an&#xA;exact URL or file.&lt;/li&gt;&#xA;&lt;li&gt;Guest bootstrap writes an atomic failure stage. Partial operations report&#xA;every failed node, stage, and error, and readiness failures point directly to&#xA;&lt;code&gt;farrow logs &amp;lt;node&amp;gt;&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Already-running guests can be rechecked without restarting QEMU. A partial&#xA;lifecycle still rebuilds the SSH client configuration from every committed&#xA;node.&lt;/li&gt;&#xA;&lt;li&gt;Netplan matches deterministic MAC addresses without renaming interfaces.&#xA;&lt;code&gt;vm_disks[].fs: auto&lt;/code&gt; prefers XFS and falls back to ext4 when necessary.&lt;/li&gt;&#xA;&lt;li&gt;The redundant &lt;code&gt;ss&lt;/code&gt; command and ambiguous root/flag shorthands are removed.&#xA;&lt;code&gt;image reset&lt;/code&gt; replaces &lt;code&gt;reset-manifest&lt;/code&gt;, which remains an alias.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;verification-boundary&#34;&gt;Verification boundary&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Source commit &lt;code&gt;da6d02426da93c677c94c67fec4eb4fcecf4766a&lt;/code&gt; passed the complete local&#xA;source gate and a full GoReleaser snapshot: unit and race tests, vet,&#xA;Staticcheck, &lt;code&gt;govulncheck&lt;/code&gt;, four target builds, image-pipeline and installer&#xA;boundaries, archive/package parity, dependency licenses, SBOMs, and native&#xA;Linux package verification. The tag workflow repeated those checks before the&#xA;Release was made public.&lt;/p&gt;</description>
      </item>
    <item>
        <title>repo.yaml Is Intent; catalog.json Is Evidence</title>
        <link>https://barn.pgsty.com/blog/design/repo-yaml-catalog-json/</link>
        <pubDate>Sat, 29 Aug 2026 19:00:00 +0800</pubDate>
        
        <guid>https://barn.pgsty.com/blog/design/repo-yaml-catalog-json/</guid>
        <description>&lt;div class=&#34;td-callout td-callout--note&#34; role=&#34;note&#34;&gt;&#xA;  &lt;div class=&#34;td-callout__title&#34;&gt;&lt;i class=&#34;td-callout__icon fa-solid fa-circle-info&#34; aria-hidden=&#34;true&#34;&gt;&lt;/i&gt;&lt;span class=&#34;td-callout__label&#34;&gt;Note&lt;/span&gt;&lt;/div&gt;&#xA;  &lt;div class=&#34;td-callout__body&#34;&gt;&#xA;&lt;p&gt;&lt;strong&gt;Renamed 2026-09-29:&lt;/strong&gt; names now follow the unreleased Barn 0.9.0 candidate.&#xA;The prior source review was on 2026-09-26: the original publication date is retained; the text&#xA;below reflects the implementation reviewed on this date. See&#xA;&lt;a href=&#34;https://barn.pgsty.com/docs/about/status/&#34;&gt;Status&lt;/a&gt; for released versus candidate behavior and&#xA;dated acceptance evidence.&lt;/p&gt;&#xA;  &lt;/div&gt;&#xA;&lt;/div&gt;&lt;p&gt;A static image repository sounds like a directory of qcow2 files plus a JSON&#xA;index. The difficult part is deciding which facts a maintainer may write by&#xA;hand and which facts must be derived from the bytes being published.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
