<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Goose on Project Wintermute</title><link>https://wintermutecore.com/tags/goose/</link><description>Recent content in Goose on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Nov 2026 14:21:36 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/goose/index.xml" rel="self" type="application/rss+xml"/><item><title>goose v3.30.1: Postgres Locker Fix and Richer ENVSUB Expansions</title><link>https://wintermutecore.com/posts/goose-v3-30-1-locker-fix-envsub-expansions/</link><pubDate>Tue, 17 Nov 2026 14:21:36 +0000</pubDate><guid>https://wintermutecore.com/posts/goose-v3-30-1-locker-fix-envsub-expansions/</guid><description>&lt;p&gt;goose, the SQL first migration tool from Pressly, shipped two releases in four days: v3.30.0 and v3.30.1. Only four commits landed in the window, but two of them matter to anyone running migrations against shared Postgres clusters from long lived processes: a lock wait fix and a much richer set of shell expansions for &lt;code&gt;+goose ENVSUB ON&lt;/code&gt;. The patch release also clears a build failure that hit users who ran &lt;code&gt;go get -u&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>