README install section is out of date for rickub.com #4
Closed@ogirardot opened this issue Sep 3, 2026 · 1 comment
- @ogirardot opened this issue · Sep 3, 2026edited
Checked against rickub.com after the v0.1.0 release:
- The README says there is no
/releases/latest/download/…redirect and that assets must be picked by hand from the release page. Bothhttps://rickub.com/rickub/cli/releases/latest/download/<asset>andhttps://rickub.com/rickub/cli/releases/download/v0.1.0/<asset>serve the archives today, so the install can be a one-liner. - It also suggests downloading "from the release's API entry", but
/api/v1has no releases endpoint (rickub api GET /repos/rickub/cli/releases→no such endpoint). - The
go buildexample usesgit describe --tags, which stampsv0.1.0, while releases stamp0.1.0.
Expected: an install snippet that downloads the right archive for the current OS/arch from the
latest/downloadURL, verifiesSHA256SUMS, and installs the binary; drop the claims about the redirect and the API entry. - The README says there is no
- @ogirardot · Sep 3, 2026edited
Fixed on main in 4f4e452 (verified against rickub.com with a rebuilt binary; ships in the next release).
Sign in to comment.