# NousResearch/hermes-agent · Git transport failures misreported as missing release during update

## Open now

- 1 issue, 2 PRs open on GitHub.
- #137244: Update resolution reports a git transport timeout as "No published stable release could be verified"
- PR #137253: fix(update): report a git transport failure as an unreachable repository, not a missing release
- PR #142554: fix(update): say GitHub couldn't be reached instead of a bare 'Update failed (exit 1)'

The three members appear to concern update/CLI messaging where a git transport failure (such as a timeout) is reported as "No published stable release could be verified" rather than as an unreachable repository. Two are fix-style changes and one is an issue describing the message; titles alone do not show their status or outcome.

## TL;DR

- 4 member(s): 1 open issue(s), 0 closed issue(s), 2 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.50`: 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.

## Open related issues

- #137244: Update resolution reports a git transport timeout as "No published stable release could be verified"

## Prior & competing PRs

- **#137253: fix(update): report a git transport failure as an unreachable repository, not a missing release**. open
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#137263`, `#137244`
  - files: `hermes_cli/source_releases.py`, `tests/hermes_cli/test_stable_lookup_git_transport.py`
- **#137263: fix(cli): name a git-leg failure as transport, not as a missing release**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#137253`, `#137244`, `#137253`
- **#142554: fix(update): say GitHub couldn't be reached instead of a bare 'Update failed (exit 1)'**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `e4e729a061ece592bcaafd007db3b0c47218977c`, `#39`
  - files: `hermes_cli/source_releases.py`, `hermes_cli/update_cmd.py`, `hermes_cli/update_cmd_check.py`, `hermes_cli/update_cmd_git.py`, `scripts/desktop-update/posix.sh`, `scripts/desktop-update/windows.ps1`, `tests/hermes_cli/test_update_fetch_failure_classifier.py`

## Fix status

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