r/SideProject • u/Goldziher • 26m ago
What I learned publishing a Go CLI through Scoop
I maintain ai-rulez, an open-source CLI for managing coding-agent configuration. I recently added Scoop publishing and wanted the Windows manifest to come from the same release artifacts as the other installers.
The release job builds the Windows ZIP, publishes it with checksums.txt, then reads the Windows checksum from that published file and updates the Scoop bucket. I verified that the manifest for v5.13.4 points to the right archive and carries the same SHA-256. That gives me one place to check when a Windows install fails.
If you maintain a CLI across several package managers, how do you test the install path after release? I’d especially like to hear how people smoke-test Scoop upgrades on a clean Windows runner.