briandevans a6485bddb8 fix(desktop): don't report a bogus update count for a shallow checkout ... The desktop installer clones with `--depth 1`, so a public install's local history often shares no merge-base with the freshly fetched origin tip. In that state `git rev-list HEAD..origin/<branch> --count` enumerates the entire remote ancestry and returns a meaningless huge number, surfacing as e.g. "v0.17.0 (+12104)" in the update indicator (#51922). The official-SSH branch of checkUpdates() already sidesteps this by reporting a binary up-to-date check (`behind: currentSha === targetSha ? 0 : 1`), and hermes_cli/banner.py guards the identical class for the CLI banner. The passive desktop count path was the one place the shallow guard was missing. Detect shallow + no-merge-base up front and fall back to the same SHA-based binary check; full clones (developers / Docker dev images) keep the exact count path unchanged. The resolution logic lives in a pure update-count.cjs helper so it is unit-testable without booting Electron.		2026-06-24 19:12:09 -05:00
..
bootstrap-installer	fix(desktop/windows): stop in-app update from cascading into a backend restart loop (#50381)	2026-06-21 13:10:32 -07:00
desktop	fix(desktop): don't report a bogus update count for a shallow checkout	2026-06-24 19:12:09 -05:00
shared	fix(desktop): move tsconfig to es2023	2026-06-15 12:07:17 -04:00