Skip redundant source-update when already at HEAD
Cluster 123314. Data as of
Nothing open on GitHub. Fix merged in #131001 on 2 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131001. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131001. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where a completed source update is incorrectly re-triggered on launch, particularly on Windows, when the stamp already matches HEAD. The fix treats exit 124 and same-commit states as non-actionable conditions rather than prompts to re-run.
Open issues0
Open PRs0
Fixes on record
-
#131001 Finished updates stay finished: no same-commit re-run on launch, Windows exit 124 after completion is success (salvage #123863, #127198)
files:
hermes_cli/post_update.py,hermes_cli/source_stamp.py,hermes_cli/venv_sync.py,scripts/desktop-update/windows.ps1,tests/hermes_cli/test_update_launch_completion.py,tests/scripts/desktop_update/test_desktop_update_windows_python_handoff.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#123863 fix(update): skip source-update completion when the stamp names HEAD · done elsewhere →
#131001
Closed issues · 1
- Closed#123314[Bug]: Fresh Windows source install enters source-update completion on first agent launch with pristine HERMES_HOME
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #131001
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Oct 2026