Summary
check_version in crates/gl/src/doctor.rs queries https://api.github.com/repos/gitlawb/releases/releases/latest to check whether the installed gl CLI is up to date. That repo path is wrong on two counts: the org segment should be Gitlawb (capitalized, matching every other reference in this codebase), and more importantly Gitlawb/releases is a separate, now-frozen repo whose last tag is v0.3.8 from 2026-03-30.
Releases have been cut directly on Gitlawb/node since v0.4.0 (2026-06-30), via release-please, and install.sh already treats Gitlawb/node as the canonical release source (REPO="${GITLAWB_RELEASE_REPO:-Gitlawb/node}", line 9). So gl doctor's version check is silently comparing against a repo that will never receive another tag.
Impact
Right now this happens to still report "up to date" by luck, since v0.3.8 sorts below the current v0.5.1. But once Gitlawb/node ships a version whose comparison against the frozen v0.3.8 tag stops mattering isn't the point: the check can never again correctly detect that an update is available, because it's asking the wrong repo. gl doctor's version check is effectively permanently broken.
Fix
Point check_version at Gitlawb/node's releases endpoint instead, matching install.sh's own source of truth.
I have a fix ready (with tests) and will open a PR referencing this issue.
Summary
check_versionincrates/gl/src/doctor.rsquerieshttps://api.github.com/repos/gitlawb/releases/releases/latestto check whether the installedglCLI is up to date. That repo path is wrong on two counts: the org segment should beGitlawb(capitalized, matching every other reference in this codebase), and more importantlyGitlawb/releasesis a separate, now-frozen repo whose last tag is v0.3.8 from 2026-03-30.Releases have been cut directly on
Gitlawb/nodesince v0.4.0 (2026-06-30), via release-please, andinstall.shalready treatsGitlawb/nodeas the canonical release source (REPO="${GITLAWB_RELEASE_REPO:-Gitlawb/node}", line 9). Sogl doctor's version check is silently comparing against a repo that will never receive another tag.Impact
Right now this happens to still report "up to date" by luck, since v0.3.8 sorts below the current v0.5.1. But once
Gitlawb/nodeships a version whose comparison against the frozen v0.3.8 tag stops mattering isn't the point: the check can never again correctly detect that an update is available, because it's asking the wrong repo.gl doctor's version check is effectively permanently broken.Fix
Point
check_versionatGitlawb/node's releases endpoint instead, matchinginstall.sh's own source of truth.I have a fix ready (with tests) and will open a PR referencing this issue.