Shipping a CLI binary still means hand-writing release pipelines for every OS, signing, checksums, and package registries per project

Every compiled CLI project still hand-rolls its own release pipeline: build scripts for three OS targets, code signing and Apple notarization wired up separately, checksums and an SBOM generated by hand, the GitHub release created manually, and custom Homebrew formula and Scoop manifest files. GoReleaser covers Go and recently added partial support for a few others but still needs a verbose config file and does not handle signing or notarization natively. cargo-dist is Rust-only, semantic-release is Node-only and handles versioning not binaries. No tool today walks into a polyglot or single-language compiled repo, infers the project type, cross-compiles to five targets, signs and notarizes the macOS binary, produces a checksum file and an SBOM, pushes a GitHub release, and updates Homebrew, Scoop, apt, and winget, all from one command with no config file required.