The Installing Jig section of docs/_ecosystem_8x/devkit/jig.md only describes two install routes: download and unpack a release tarball, or go install. Since jig v2.3.0 (July 2026) the releases also ship native packages that the page doesn't mention.
Assets attached to every release from v2.3.0 onward:
jig_<version>_linux_{amd64,arm64}.debjig_<version>_linux_{amd64,arm64}.rpmjig_<version>_{linux,darwin}_{amd64,arm64}.tar.gzjig_<version>_windows_amd64.zipsha256sums.txt
The .deb and .rpm are built by goreleaser's nfpm stage (nfpms: in .goreleaser.yaml): package name jig, vendor Vox Pupuli, license GPL-3.0-or-later, installs the binary plus /usr/share/doc/jig/LICENSE. They are standalone package files attached to the GitHub release; there is no apt or yum repository to subscribe to.
Proposed changes
- Add a Linux packages subsection showing
dpkg -i / apt install ./jig_*.deb and dnf install ./jig_*.rpm (or rpm -i) from a downloaded release asset, and note that upgrades mean downloading the next release's package.
- Mention the Windows
.zip alongside the tarballs, since the current text says "uncompress it" without saying which archive type each platform gets.
- Point at
sha256sums.txt for verifying downloads.
- Keep the tarball and
go install routes, and restate that the macOS Gatekeeper tip applies to the unsigned darwin tarballs.
- Check whether the section belongs in a 9.x ecosystem collection as well when one exists; today only
_ecosystem_8x (symlinked as _ecosystem_latest) carries the DevKit pages.
Upstream's own docs/installation.md still only covers building from source, so there's nothing to link to for the package route yet.
Also: the go install command installs jig 1.x
jig's go.mod declares module github.com/voxpupuli/jig/v2, and the v1.x tags still exist. That means the command on the page today,
go install github.com/voxpupuli/jig@latest
resolves @latest against the v1 module path and installs v1.5.0, not 2.4.0. The correct form is:
go install github.com/voxpupuli/jig/v2@latest
Upstream tracking for their own install docs: voxpupuli/jig#96.
The Installing Jig section of
docs/_ecosystem_8x/devkit/jig.mdonly describes two install routes: download and unpack a release tarball, orgo install. Since jig v2.3.0 (July 2026) the releases also ship native packages that the page doesn't mention.Assets attached to every release from v2.3.0 onward:
jig_<version>_linux_{amd64,arm64}.debjig_<version>_linux_{amd64,arm64}.rpmjig_<version>_{linux,darwin}_{amd64,arm64}.tar.gzjig_<version>_windows_amd64.zipsha256sums.txtThe
.deband.rpmare built by goreleaser's nfpm stage (nfpms:in.goreleaser.yaml): package namejig, vendor Vox Pupuli, license GPL-3.0-or-later, installs the binary plus/usr/share/doc/jig/LICENSE. They are standalone package files attached to the GitHub release; there is no apt or yum repository to subscribe to.Proposed changes
dpkg -i/apt install ./jig_*.debanddnf install ./jig_*.rpm(orrpm -i) from a downloaded release asset, and note that upgrades mean downloading the next release's package..zipalongside the tarballs, since the current text says "uncompress it" without saying which archive type each platform gets.sha256sums.txtfor verifying downloads.go installroutes, and restate that the macOS Gatekeeper tip applies to the unsigned darwin tarballs._ecosystem_8x(symlinked as_ecosystem_latest) carries the DevKit pages.Upstream's own docs/installation.md still only covers building from source, so there's nothing to link to for the package route yet.
Also: the
go installcommand installs jig 1.xjig's
go.moddeclaresmodule github.com/voxpupuli/jig/v2, and thev1.xtags still exist. That means the command on the page today,go install github.com/voxpupuli/jig@latestresolves
@latestagainst the v1 module path and installs v1.5.0, not 2.4.0. The correct form is:go install github.com/voxpupuli/jig/v2@latestUpstream tracking for their own install docs: voxpupuli/jig#96.