<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Go on rmqa.com</title>
    <link>https://rmqa.com/tags/go/</link>
    <description>Recent content in Go on rmqa.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rmqa.com/tags/go/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Real Release Checked With rmqa, ukue 0.1.0 From GitHub</title>
      <link>https://rmqa.com/a-real-release-checked-with-rmqa-ukue-0.1.0-from-github/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/a-real-release-checked-with-rmqa-ukue-0.1.0-from-github/</guid>
      <description>&lt;p&gt;The other use cases on this site use a made-up tool so the mistakes can be planted on purpose. This one is a real release: &lt;a href=&#34;https://ukue.com/&#34;&gt;ukue&lt;/a&gt;, a job queue that lives in one SQLite file, published on GitHub as five archives and a checksums file. Like rmqa, it&amp;rsquo;s a &lt;a href=&#34;https://softdevstudio.com/&#34;&gt;SoftDevStudio.com&lt;/a&gt; project, and its releases are built by a workflow nobody watches.&lt;/p&gt;&#xA;&lt;h2 id=&#34;writing-the-manifest&#34;&gt;Writing the Manifest&lt;/h2&gt;&#xA;&lt;p&gt;The files came straight from the release&amp;rsquo;s download links. Then:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wrong Build in the arm64 Archive Caught Before a Go CLI Release Went Out</title>
      <link>https://rmqa.com/wrong-build-in-the-arm64-archive-caught-before-a-go-cli-release-went-out/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/wrong-build-in-the-arm64-archive-caught-before-a-go-cli-release-went-out/</guid>
      <description>&lt;p&gt;Say a small team maintains a command-line tool in Go called &lt;code&gt;tidy&lt;/code&gt;. Each release ships five archives, for Linux on Intel and ARM, macOS on Apple silicon and Intel, and Windows, plus a &lt;code&gt;SHA256SUMS&lt;/code&gt; file. A release workflow builds them in a matrix of jobs and a final job uploads everything.&lt;/p&gt;&#xA;&lt;p&gt;One day a refactor of the workflow moves the build output into a shared folder. The Linux ARM job now packs whatever &lt;code&gt;tidy&lt;/code&gt; binary is in that folder, and on the runner where it lands, that&amp;rsquo;s the Intel build. Meanwhile the Intel Mac job hits a cache from the previous release and doesn&amp;rsquo;t rebuild. Every job is green. The archives have the right names and plausible sizes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
