https://arran4.github.io/blog/tags/release/Recent content in release on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Mon, 13 Jul 2026 16:58:16 +1000https://arran4.github.io/blog/post/2026/023-assembling-goreleaser-yaml/Mon, 13 Jul 2026 16:58:16 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/023-assembling-goreleaser-yaml/Over time, I&rsquo;ve created numerous .goreleaser.yaml files for various projects. While a lot of them are out of date and inconsistent, reviewing them has helped me formulate a standard set of practices for assembling a GoReleaser configuration file. This post outlines these standards to help maintain consistency, maximize distribution, and simplify CI processes across projects. General Principles Naming Packages I believe that the defaults should work for file and package naming, so I avoid using _template for naming (such as renaming things) unless it is strictly required to prevent a name conflict.