Skip to content

logos doctor --check-updates says when logos is out of date - #125

Merged
Coder8124 merged 1 commit into
mainfrom
doctor-update-check
Nov 9, 2026
Merged

Coder8124 merged 1 commit into
mainfrom
doctor-update-check

Conversation

@Coder8124

Copy link
Copy Markdown
Owner

logos doctor --check-updates adds a version row: ok when this binary is the latest release (or ahead of it), to do with the upgrade command when it is behind, unchecked with the reason when GitHub could not be reached or the build is an unstamped dev build.

  • The fix matches how logos was installed: brew upgrade logos-mcp, npm i -g @noeton/logos@latest, npx @noeton/logos@latest, or logos update.
  • Opt-in only. A plain logos doctor stays offline and prints one line naming the flag, so silence about the version is not read as "up to date".
  • It is the same single bare GET as logos update --check (selfupdate.CheckOnly, 10s timeout). doctor --egress lists it, and the selfupdate package comment now says doctor makes it only under this flag.
  • Versions are compared as versions, so a 0.5.8 binary against a v0.5.8 tag is current.

Verified: go build/test (47 ok)/vet (+ Windows)/gofmt, chaos tier; 7 new tests against an httptest GitHub (two mutation-checked); a binary stamped 0.5.6 on a scratch vault reports "logos 0.5.6 is out of date; the latest release is v0.5.7 → logos update".

@Coder8124
Coder8124 merged commit 1c31a61 into main Nov 9, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant