go/goreleaser
go/goreleaser
1
0
Fork 0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-01-24 04:16:27 +02:00
Code Issues Releases Activity
goreleaser/www/docs/blog/posts/2023-01-30-goreleaser-v1.15.md
Carlos Alexandro Becker f62adf23ff
docs: blog (#4264) 
Starting to move the blog from medium to mkdocs!

closes #3503

---------

Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
2023-09-14 13:53:40 -03:00

2.7 KiB
Raw Blame History

date slug categories authors
2023-01-30 goreleaser-v1.15
announcements
caarlos0

Announcing GoReleaser v1.15 — the first of 2023

Keeping our pace of 1 minor a month, this is the January 2023 release.

GoReleaser’s Ko integration documentation

It is packed with some juicy features and tons of bug fixes and quality-of-life improvements.

Let's take a look:

Highlights

  • GoReleaser Pro now can now create changelog subgroups
  • You can create and push Docker images/manifests with Ko (big thanks to @developerguyba and @ImJasonH for all the work here)
  • More templateable fields: nfpms.apk.signature.key_name, release.disable, release.skip_upload, snaps.grade, telegram.chat_id
  • Deprecated --clean in favor of --clean
  • As always, a lot of bug fixes and documentation improvements

You can install the same way you always do, and you can see the full release notes here and here (for Pro).

GitHub Action incident

Last Friday (Jan 27th), we had a rather big incident due to a GitHub website change. We were using a URL to get the release that was not in the API domain, but was working well for a couple of years. GitHub changed it, and we, as well as many other projects, got an incident in our hands. This is definitely our fault, though, we should have been using the guaranteed API endpoints instead. That said, we fixed it rather quickly, even though it was a Friday night. Since then, we also made more changes to use the releases.json served by our website instead of GitHub’s API, which also avoids rate limits and issues with GHE users. I also wanna give huge props to @crazy-max for working hard on all that, as well as everyone who helped debug and test everything on #389.

Other news