Add riscv64 to release binaries

[gounthar]

Is your feature request related to a problem? Please describe.

There are no riscv64 release binaries for lazygit. Users on RISC-V hardware (e.g. VisionFive 2, LicheePi 4A, SiFive boards) must build from source, which is straightforward but inconvenient for a pure Go project that already ships arm64 and armv6 binaries.

Describe the solution you'd like

Add riscv64 to the goarch list in .goreleaser.yml:

    goarch:
      - amd64
      - arm
      - arm64
      - '386'
      - riscv64

Since lazygit builds with CGO_ENABLED=0, the riscv64 target requires no special toolchain or cross-compilation setup. Go has supported GOARCH=riscv64 as a first-class target since Go 1.14.

This would produce lazygit_<version>_linux_riscv64.tar.gz (and freebsd_riscv64) in each release, with no changes to the build pipeline itself.

Describe alternatives you've considered

• Building from source on the target board. This works but means riscv64 users cannot use package managers or install scripts that pull release binaries.
• Distribution-level packaging (Arch RISC-V, Debian ports). Some distros carry lazygit already, but official release binaries are the most portable option.

Additional context

Lazygit builds successfully on native riscv64 hardware. The test suite passes except for one timing-sensitive test (TestNewCmdTaskInstantStop) that hits a race condition on slower hardware, not related to riscv64 support itself.

Build and test run on native riscv64: https://github.com/gounthar/lazygit/actions/runs/23536886583

Happy to open a PR if this seems reasonable.

[stefanhaller]

@gounthar I know nothing about RISC-V hardware, so I can't tell how widespread it is, or how likely users of such hardware are to want to run lazygit on it. Can you give any input on that?

[gounthar]

Fair question. RISC-V is still a niche architecture compared to ARM or x86, but it is growing. There are a handful of single-board computers (StarFive VisionFive 2, Milk-V Pioneer, SpacemiT K1-based boards like BananaPi F3) running Linux, and some development servers are starting to appear.

The user base is small today, mostly developers and early adopters who run standard Linux tools. lazygit is the kind of tool those users would reach for. The change itself is a one-line addition to GoReleaser with no maintenance burden since Go cross-compiles riscv64 out of the box with CGO_ENABLED=0.

That said, I understand if the team prefers to wait until the ecosystem is more established. No pressure either way.

[stefanhaller]

Ok, thanks. This does sound like it's not terribly important to add right now.

[gounthar]

No worries, thanks for considering it. The PR is a one-line GoReleaser change if you ever want it. Happy to open one whenever.