GoReleaser v2.18 is out!
- release summaries straight into your GitHub Actions job summary
- preflight checks that fail before you build
- OpenTelemetry traces of your releases
- publish to Iru Custom Apps
- a lot of bug fixes!
goreleaser.com/blog/goreleas…
GoReleaser v2.17 🚀
The new verify pipe re-downloads your published release assets and runs your own checks against them — catching broken uploads, bad signatures & CDN issues after the release "succeeded".
Plus Windows .msix, RISC-V & more:
goreleaser.com/blog/goreleas…
I wrote a small tool to keep sponsor lists up to date in @goreleaser website and its many READMEs.
It fetches data from GitHub sponsors and from OpenCollective, and you can use Go templates to apply it anywhere.
It's mostly for me, so there's rough edges there, but here you go in case you think it might be useful:
carlosbecker.com/posts/spons…
Yet another great feature coming to a GoReleaser next to you: historically, if you had multiple `main` funcs in your project, you'd need to setup several `builds` in GoReleaser's configuration.
No more.
Set `main: ./...` and let it rip.
It'll walk your repo, find all the 'func main', infer binary names, and build them all in a single `go build` exec!
Still on the works, happy to hear your feedback!
See: github.com/goreleaser/gorele…
Who knows how to secure open source better than the maintainers themselves? 🛡️
In Session 3 of the GitHub Secure Open Source Fund, 67 more projects improved their defenses.
From securing the AI stack to strengthening the global supply chain, find out how these maintainers are making security improvements that benefit the entire ecosystem. 👇
github.blog/open-source/main…