github.com/goreleaser/goreleaser@v1.25.1/www/docs/blog/posts/2023-01-30-goreleaser-v1.15.md (about)

     1  ---
     2  date: 2023-01-30
     3  slug: goreleaser-v1.15
     4  categories:
     5    - announcements
     6  authors:
     7    - caarlos0
     8  ---
     9  
    10  # Announcing GoReleaser v1.15 — the first of 2023
    11  
    12  Keeping our pace of 1 minor a month, this is the January 2023 release.
    13  
    14  <!-- more -->
    15  
    16  ![GoReleaser’s Ko integration documentation](https://carlosbecker.com/posts/goreleaser-v1.15/img.png)
    17  
    18  It is packed with some juicy features and tons of bug fixes and quality-of-life
    19  improvements.
    20  
    21  Let's take a look:
    22  
    23  ### Highlights
    24  
    25  - GoReleaser Pro now can now create changelog subgroups
    26  - You can create and push Docker images/manifests with [Ko](https://ko.build/)
    27    (big thanks to [@developerguyba](https://twitter.com/developerguyba) and
    28    [@ImJasonH](https://twitter.com/ImJasonH) for all the work here)
    29  - More templateable fields: `nfpms.apk.signature.key_name`, `release.disable`,
    30    `release.skip_upload`, `snaps.grade`, `telegram.chat_id`
    31  - Deprecated `--clean` in favor of `--clean`
    32  - As always, a lot of bug fixes and documentation improvements
    33  
    34  You can [install][] the same way you always do, and you can see the full release
    35  notes [here][oss-rel] and [here (for Pro)][pro-rel].
    36  
    37  [install]: https://goreleaser.com/install
    38  [pro-rel]: https://github.com/goreleaser/goreleaser-pro/releases/tag/v1.15.0-pro
    39  [oss-rel]: https://github.com/goreleaser/goreleaser/releases/tag/v1.15.0
    40  
    41  #### GitHub Action incident
    42  
    43  Last Friday (Jan 27th), we had a rather big
    44  [incident](https://github.com/goreleaser/goreleaser-action/pull/389) due to a
    45  GitHub website change. We were using a URL to get the release that was not in
    46  the API domain, but was working well for a couple of years. GitHub changed it,
    47  and we, as well as many other projects, got an incident in our hands. This is
    48  definitely our fault, though, we should have been using the guaranteed API
    49  endpoints instead. That said, we fixed it rather quickly, even though it was a
    50  Friday night. Since then, we also made more changes to use the `releases.json`
    51  served by our website instead of GitHub’s API, which also avoids rate limits and
    52  issues with GHE users. I also wanna give huge props to
    53  [@crazy-max](https://github.com/crazy-max) for working hard on all that, as well
    54  as everyone who helped debug and test everything on
    55  [#389](https://github.com/goreleaser/goreleaser-action/pull/389).
    56  
    57  ### Other news
    58  
    59  - GoReleaser now has ~11.2k stars and 322 contributors! Thanks, everyone!
    60  - We are now present in the fediverse, give us a follow at
    61    [@goreleaser@fosstodon.org](https://fosstodon.org/@goreleaser).
    62  - We eventually discuss new features in our Discord server. 
    63    [Join the conversation](https://goreleaser.com/discord)!
    64  - nFPM had new releases as well, 
    65    [check it out](https://github.com/goreleaser/nfpm/releases).