Publish The Binary to various package management systems

[Vad1mo]

As a user, I would rather not download the source code, compile to have binary.
A common practice for downloading and installing CLI tools is the use of popular Package Manager like Chocolatey on Win or Homebrew on Mac and so on.

One way to accomplish is to create a pipeline for each package manager.

Another alternative to have an all-in-one solution is to use https://jreleaser.org/ that provides many option to release and publish the binary to many package management systems. see full list https://jreleaser.org/guide/latest/integrations.html#_package_publish

At least we should support the following option

• Homebrew
• Docker
• Chocolatey
• AppImage

[amands98]

we can also explore

• Nix
• Snap

[amands98]

we can utilize goreleaser.

[Vad1mo]

Didn't know about goreleaser. but will look into it.

[aalmiray]

Both GoReleaser and JReleaser work in similar ways. However, the funtamental difference between these tools is that GoReleaser has tight integration with the Go build tool chain (it can build and release binaries) while JReleaser does not build binaries (it might assemble archives though) and expects target binaries to be given as inputs.

Both tools offer similar features (there's a large intersection) while at the same time provide unique features.
For this reason, it's recommended to use GoReleaser for Golang projects, JReleaser for everything else. Although, nothing stops you from using JReleaser with Golang projects, it's just that you'll have to configure a build step that's separate from the release step.

[amands98]

Check out the PR, I added goreleaser support.

[prashantrewar]

+1 to @amands98 @aalmiray, jreleaser is inspired by goreleaser.

[amands98]

⚪ homebrew - Homebrew/homebrew-core#165860
⚪ winget microsoft/winget-pkgs#144972