<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Releases on Barn</title>
    <link>https://barn.pgsty.com/tags/releases/</link>
    <description>Recent content in Releases on Barn</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Mon, 09 Nov 2026 00:00:00 +0800</lastBuildDate>
    
    
      <atom:link href="https://barn.pgsty.com/tags/releases/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>From Upstream Images to a Signed Catalog</title>
        <link>https://barn.pgsty.com/blog/design/image-update-evidence/</link>
        <pubDate>Sun, 08 Nov 2026 10:00:00 +0800</pubDate>
        
        <guid>https://barn.pgsty.com/blog/design/image-update-evidence/</guid>
        <description>&lt;p&gt;An image audit answers a narrower question than an image release. It can find a newer upstream file, but Barn may add that file to its signed catalog only after the artifact, runtime profile, and boot path have all been verified. The &lt;a href=&#34;https://barn.pgsty.com/docs/reference/images/&#34;&gt;image reference&lt;/a&gt; describes the user-facing catalog; this essay records the reasoning that keeps catalog updates reproducible.&lt;/p&gt;&#xA;&lt;h2 id=&#34;four-meanings&#34;&gt;Four meanings of “new”&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Image work becomes error-prone when four independent version values are treated as one:&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
