ETA since I just saw Christian chime in: the Goreleaser author works at Charm.sh =)
And actually Carlos, who builds GoReleaser, is the true author of Fang and took it from concept to execution.
That said, I am unfamiliar with any licensing for Windows builds.
MacOS has some niche (usually discarded) technicalities like you can only use the SDK on Apple hardware.
(Hello from Charm! I’m one of the authors of this library.)
I started a similar thing, although not as feature-rich as yours. My goal was to follow CLI best practices and add all the boilerplate one needs to build a Rust CLI.
for speed you can look for vendors like https://depot.dev/
Though my motivation for this was getting the builds off my machine. I didn't want to be shipping binaries I had built locally.
Throughout these years, I have found that cross-compiling is the most challenging part of creating a CLI. When you are building a web back-end, you control the execution environment (usually linux). For CLIs, your users could be on Linux, macOS or Windows. You need to get three x2 binaries (so a total of 6) to have a fair coverage.
I’ve tried cross, but for Windows and macOS you need licenses. There is no straightforward way to give your users Docker images and have them running in a few commands. You can compile on GitHub action machines, but that’s a very slow feedback loop. I wonder if things are better in Go land.
!: https://github.com/rust-starter/rust-starter