Source version reporting and update tag issues
Cluster 122054 · hermes cli. Data as of
1 open item. Fix merged in #122208 on 25 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #122208. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #122208, then check whether your report is the one still open.
Read #122208Pick up a Lab taskThese items relate to bugs and fixes around how source installs report their current version and how release tags are handled during source updates. The work addresses a mismatch between reported source versions and catalog plugin requirements.
Open issues1
- Issue#122054[Bug]: Current source version is older than catalog plugin requirements
Open PRs0
Fixes on record
-
#122208 fix(update): source installs report the current release after updating
files:
hermes_cli/gitlock.py,hermes_cli/update_cmd_maint.py,tests/hermes_cli/test_source_completion_stamp.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#122065 fix(update): let release tags travel with the fetched source update · superseded by another PR →
#122208,#122054
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
- Subsystem
- hermes cli
- Merged PRs
- #122208
- Closed issues
- 0
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 Sep 2026