<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Homebrew on nsys.dev Tech Blog</title>
		<link>https://blog.nsys.dev/en/tags/homebrew/</link>
		<description>Recent content in Homebrew on nsys.dev Tech Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 15 Jun 2026 14:00:00 +0900</lastBuildDate>
		
			<atom:link href="https://blog.nsys.dev/en/tags/homebrew/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Shipping a CLI with brew and scoop — all at once via GoReleaser</title>
				<link>https://blog.nsys.dev/en/posts/brew-scoop-release/</link>
				<pubDate>Mon, 15 Jun 2026 14:00:00 +0900</pubDate>
				<guid>https://blog.nsys.dev/en/posts/brew-scoop-release/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Part 4 of 5&lt;/strong&gt; — series: &lt;em&gt;Building a publishing tool, and shipping it&lt;/em&gt;. Last time was &lt;a href=&#34;https://blog.nsys.dev/en/posts/i18n-design/&#34;&gt;designing a multilingual site&lt;/a&gt;. See the &lt;a href=&#34;https://blog.nsys.dev/en/tags/crofty/&#34;&gt;series index&lt;/a&gt;. This time: the practical side of shipping with brew and scoop.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Once the CLI exists, the next question is &amp;ldquo;how do I ship it?&amp;rdquo; &lt;code&gt;go install&lt;/code&gt; works, but being installable with Homebrew or Scoop is much easier on the people using it.&lt;/p&gt;&#xA;&lt;p&gt;That said, building by hand for mac, Windows, and Linux, then hand-writing a Homebrew formula and a Scoop manifest… isn&amp;rsquo;t something you keep doing every release. So I had GoReleaser do it all in one go — including the one place macOS tripped me up (signing).&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
