Skip to content

fix: resolve latest to actual release tag before downloading#18

Merged
ClayMav merged 2 commits intomainfrom
fix/resolve-latest-release-tag
Apr 6, 2026
Merged

fix: resolve latest to actual release tag before downloading#18
ClayMav merged 2 commits intomainfrom
fix/resolve-latest-release-tag

Conversation

@ClayMav
Copy link
Copy Markdown
Member

@ClayMav ClayMav commented Apr 6, 2026

Summary

  • gh release download does not support latest as a magic alias — it requires a real tag name
  • Both the install script and wherobots upgrade now resolve latest to the actual latest release tag via gh release view before downloading
  • Fixes: release not found error when running the install script or upgrade command

Test plan

  • go test ./... passes
  • go build ./... compiles
  • Tested install script end-to-end — successfully installed v1.0.0

gh release download does not support "latest" as a magic alias — it
requires a real tag name. Both the install script and upgrade command
now resolve "latest" via gh release view first.
@ClayMav ClayMav requested a review from a team as a code owner April 6, 2026 21:40
@ClayMav ClayMav requested a review from sfishel18 April 6, 2026 21:40
The install script, upgrade command, and version check all previously
shelled out to the gh CLI. Since the repo is public, no authentication
is needed. This replaces every gh invocation with:

- net/http calls to the GitHub releases API (for resolving latest tag)
- Direct HTTP downloads from GitHub release asset URLs
- curl in the install script (with grep/sed to parse JSON, no jq needed)
@ClayMav ClayMav merged commit 61e13ba into main Apr 6, 2026
1 check passed
@ClayMav ClayMav deleted the fix/resolve-latest-release-tag branch April 6, 2026 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants