fix: update self-references after repo rename to wherobots-cli - #34
Merged
Conversation
The GitHub repo wherobots/wbc-cli was renamed to wherobots/wherobots-cli (WBC-758). The CLI's self-upgrade command and background update-check, plus the install script and docs, still pointed at the old owner/name. GitHub redirects the old path for now, so nothing is broken today. But redirects lapse the moment someone recreates a repo named wbc-cli, at which point self-upgrade and update-check would silently hit the wrong repo. Point every internal reference at the real name so behavior is correct regardless of redirects. Changes: - internal/version/check.go: update-check repo constant - internal/commands/upgrade.go: self-upgrade repo constant - scripts/install-release.sh: default REPO and usage text - README.md: raw install URLs, git clone URL, and clone dir - RELEASE.md: gh api repos/... path go.mod module path (wherobots/cli) and the binary name are unaffected.
ClayMav
marked this pull request as ready for review
July 21, 2026 17:22
There was a problem hiding this comment.
Reviewed by Salty Hambot 🤖🧂 — rubric mode
Verdict: ✅ pass
| Dimension | Verdict | Notes |
|---|---|---|
| correctness | ✅ pass | Repo string updated consistently in all four self-referencing locations; no logic touched. |
| security | ✅ pass | No auth, injection, or credential handling changed — pure string rename. |
| privacy | ✅ pass | No data handling or PII surface affected. |
| reliability | ✅ pass | Existing binaries carry the old constant until a fresh release cuts, but the author already flagged this follow-up; no regression in the code itself. |
| scalability | ✅ pass | No performance or load-bearing paths touched. |
| observability | ✅ pass | Log/error messages already reference the constant, so they update transitively; nothing to add. |
| clarity/maintainability | ✅ pass | Rename improves clarity by matching the actual repo name; docs and code stay in sync. |
| test quality | ✅ pass | No existing tests hardcode the repo string, so nothing breaks and no new tests are warranted for a rename. |
Textbook find-and-replace rename to wherobots-cli — consistent across README, RELEASE.md, both Go constants, and the install script, with no stale wbc-cli stragglers. Ship it (and don't forget to cut that fresh release so old binaries can self-heal).
0 finding(s) posted · 1 skipped as already raised.
💰 Review cost: $0.4951 · 469.1k in / 4.3k out tokens · ⏱️ 3m13.6s
💬 To request a re-review, comment @salty-hambot review
peterfoldes
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The GitHub repo
wherobots/wbc-cliwas renamed towherobots/wherobots-cli. This updates all internal self-references so the CLI's self-upgrade, background update-check, install script, and docs point at the new name.Linear: WBC-758
Why
GitHub currently redirects the old
wherobots/wbc-clipath, so nothing is broken today. But that redirect lapses the moment anyone recreates a repo namedwbc-cliunder the org — at which point:wherobots upgrade(self-upgrade) would fetch releases from the wrong repoPointing every internal reference at the real name makes behavior correct regardless of redirects.
Changes
internal/version/check.gorepoconstant used for update-checkinternal/commands/upgrade.goupgradeRepoconstant used for self-upgradescripts/install-release.shREPO+ usage/help textREADME.mdgit cloneURL, and clone directory (cd wherobots-cli)RELEASE.mdgh api repos/...release-notes pathNot changed:
go.modmodule path (wherobots/cli) and the binary name (wherobots) — both independent of the repo name.Verification
go build ./...— cleango test ./...— all pass (incl.internal/version,internal/commands)gofmt -l internal/— clean;go vet ./...— cleanwherobots/wherobots-cli.Follow-up
A new release should be cut after merge so that already-installed binaries (which still carry the old
wherobots/wbc-cliconstant) self-upgrade against the new repo name.