You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cargo binstall judgment installs the release's jud tarball instead of
compiling: [package.metadata.binstall] in Cargo.toml names the asset
and the binary's path inside it, and the release workflow checks, on every
platform it packages, that the templates name the tarball it just built
(The jud command line).
A Homebrew formula for jud: brew install chussenot/tap/jud on Apple
silicon and Linux, from chussenot/homebrew-tap.
The formula installs the release tarballs by their checksums and generates
the shell completions from the binary. It is rendered from each release's SHA256SUMS by scripts/homebrew-formula.sh and committed to the tap by
the release workflow's new homebrew job, so the tap's version is the
release's (The jud command line, Releasing).