# NousResearch/hermes-agent · PyPI version gap mislabeled as commit count in banner

## Open now

- 0 issues, 1 PR open on GitHub.
- PR #61419: fix(banner): use 'version' not 'commit' when update count may come from PyPI

These items address a bug where the update banner incorrectly describes a PyPI version difference using git commit language, most notably in Docker environments that lack git history.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #35857: \[Bug\]: Banner shows "1 commit behind" inside Docker even though no git history exists — PyPI fallback mislabels version gap as literal commits

## Prior & competing PRs

- **#35881: fix(banner): don't render PyPI version delta as '1 commit behind' (#35857)**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#61419: fix(banner): use 'version' not 'commit' when update count may come from PyPI**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`
  - files: `hermes_cli/banner.py`, `tests/hermes_cli/test_update_check.py`, `ui-tui/src/components/branding.tsx`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`