<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Goreleaser on rmqa.com</title>
    <link>https://rmqa.com/tags/goreleaser/</link>
    <description>Recent content in Goreleaser 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/goreleaser/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Checking a Draft GitHub Release Before Anyone Can Download It</title>
      <link>https://rmqa.com/checking-a-draft-github-release-before-anyone-can-download-it/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/checking-a-draft-github-release-before-anyone-can-download-it/</guid>
      <description>&lt;p&gt;Many projects don&amp;rsquo;t publish releases straight from CI. A tool such as GoReleaser builds everything and uploads it to a draft release on GitHub. A maintainer looks the draft over, edits the notes, and presses publish. Until then, nobody else can see it.&lt;/p&gt;&#xA;&lt;p&gt;That review step is a good idea with one weakness: a person looking at a list of six file names can&amp;rsquo;t tell what&amp;rsquo;s inside them. The draft is the last moment a mistake is free to fix, and it&amp;rsquo;s exactly where an automatic check belongs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
