multica-ai/multica · error
could not determine latest version; check https://github.com
Error message
could not determine latest version; check https://github.com/multica-ai/multica/releases/latest
What it means
The update command is not running under Homebrew, so it needs the latest release tag from cli.FetchLatestRelease() to build the download URL — but that call failed earlier (a warning was printed: 'could not check latest version'), leaving `latest == nil`. Without a tag there is nothing to download, so the command aborts and points the user at the GitHub releases page.
Source
Thrown at server/cmd/multica/cmd_update.go:61
}
fmt.Fprintf(os.Stderr, "Latest version: %s\n\n", latest.TagName)
}
// Detect installation method and update accordingly.
if cli.IsBrewInstall() {
fmt.Fprintln(os.Stderr, "Updating via Homebrew...")
output, err := cli.UpdateViaBrew()
if err != nil {
fmt.Fprintf(os.Stderr, "%s\n", output)
return fmt.Errorf("brew upgrade failed: %w\nYou can try manually: brew upgrade multica-ai/tap/multica", err)
}
fmt.Fprintln(os.Stderr, "Update complete.")
return nil
}
// Not installed via brew — download binary directly from GitHub Releases.
if latest == nil {
return fmt.Errorf("could not determine latest version; check https://github.com/multica-ai/multica/releases/latest")
}
targetVersion := latest.TagName
fmt.Fprintf(os.Stderr, "Downloading %s from GitHub Releases...\n", targetVersion)
output, err := cli.UpdateViaDownloadWithTimeout(targetVersion, updateDownloadTimeout)
if err != nil {
return fmt.Errorf("update failed: %w", err)
}
fmt.Fprintf(os.Stderr, "%s\nUpdate complete.\n", output)
return nil
}
View on GitHub (pinned to 2c0912b6ec)
Solutions
- Check network/proxy access to https://api.github.com and https://github.com/multica-ai/multica/releases.
- Retry once transient network conditions or rate limits clear (unauthenticated GitHub API is limited to 60 req/h).
- If a GITHUB_TOKEN-style mechanism is supported by your setup, use it to raise the rate limit.
- As a workaround, download the binary manually from the releases page the error links to.
Defensive patterns
Strategy: retry
Validate before calling
curl -fsS --max-time 10 https://api.github.com/repos/multica-ai/multica/releases/latest >/dev/null \ && echo 'github reachable' || echo 'github unreachable: update will fail'
Try / catch
for i in 1 2 3; do multica update && break; echo "attempt $i failed (likely network)"; sleep 30; done
Prevention
- Ensure network/proxy access to api.github.com before scripting updates.
- Cache the last-known release tag so offline runs can skip the check.
- Prefer the Homebrew install path where brew already handles retrying.
When it happens
Trigger: Running `multica update` on a non-brew install while GitHub API/releases are unreachable (offline, proxy blocking api.github.com, rate limit) — the earlier FetchLatestRelease error is downgraded to a warning, then this guard fires at the download step.
Common situations: Corporate proxies or sandboxes that block api.github.com, GitHub API rate limiting from shared IPs, DNS failures, or air-gapped machines.
Related errors
- brew upgrade failed: %w You can try manually: brew upgrade m
- update failed: %w
- create agent: %w
- update agent: %w
- list agent tasks: %w
AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15).
Data as JSON: /api/errors/ab648603baef38e8.
Report an issue: GitHub.