[GH-ISSUE #851] Windows Binaries are being released as .tar.gz's #394

New issue

Closed

opened 2026-02-25 23:34:08 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:34:08 +03:00

Owner

Originally created by @torculus on GitHub (Feb 29, 2024).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/851

Just like it says, the releases page distributes Windows .exe's in .tar.gz files. These can't be opened natively on Windows, and it's blocking submission of shiori to winget

Here's the relevant section in goreleaser:
github.com/go-shiori/shiori@595cb45a2c/.goreleaser.yaml (L29)

Another golang project I follow solves this with this setting

  format_overrides:
  - goos: windows
    format: zip

Originally created by @torculus on GitHub (Feb 29, 2024). Original GitHub issue: https://github.com/go-shiori/shiori/issues/851 Just like it says, the releases page distributes Windows `.exe`'s in `.tar.gz` files. These can't be opened natively on Windows, and it's blocking submission of `shiori` to `winget` Here's the relevant section in goreleaser: https://github.com/go-shiori/shiori/blob/595cb45a2ce7031926ead1f1e1324e673e36d676/.goreleaser.yaml#L29 Another golang project I follow [solves this](https://github.com/twpayne/chezmoi/blob/master/.goreleaser.yaml#L99) with this setting ```yaml format_overrides: - goos: windows format: zip ```

kerem

2026-02-25 23:34:08 +03:00

closed this issue
added the
type:enhancement
label

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@Monirzadeh commented on GitHub (Feb 29, 2024):

Do you test

https://github.com/goreleaser/goreleaser/pull/4081

@Monirzadeh commented on GitHub (Feb 29, 2024): Do you test https://github.com/goreleaser/goreleaser/pull/4081

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@torculus commented on GitHub (Feb 29, 2024):

@Monirzadeh no, for several reasons:

Most importantly: effort. Releasing as a .zip requires minimal effort, while releasing for winget requires registering with the Microsoft contributor covenant and (possibly) creating a new git branch or repo just for winget manifest updates
The winget manifest schema changes every few months, and there are plenty of broken/barely-working packages in winget which are the result of automated updates
There may be some Windows users who can't/don't want to use winget. Distributing as a .zip also allows for people to test shiori without installing it

Although it is possible to overcome each of those issues, releasing as a .zip is probably a good place to start right now. Winget support can always be added later 🙂

@torculus commented on GitHub (Feb 29, 2024): @Monirzadeh no, for several reasons: 1. Most importantly: effort. Releasing as a `.zip` requires minimal effort, while releasing for `winget` requires registering with the Microsoft contributor covenant and (possibly) creating a new git branch or repo just for `winget` manifest updates 2. The `winget` manifest schema changes every few months, and there are plenty of broken/barely-working packages in `winget` which are the result of automated updates 3. There may be some Windows users who can't/don't want to use winget. Distributing as a `.zip` also allows for people to test `shiori` without installing it Although it is possible to overcome each of those issues, releasing as a `.zip` is probably a good place to start ***right now***. Winget support can always be added later 🙂

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@Monirzadeh commented on GitHub (Feb 29, 2024):

Thanks for details

@Monirzadeh commented on GitHub (Feb 29, 2024): Thanks for details

kerem commented

2026-02-25 23:34:08 +03:00

Author

Owner

@fmartingr commented on GitHub (Apr 13, 2024):