NousResearch/hermes-agent
Skills lock content_hash causing false update_available
Cluster 41176 · skills. Data as of
3 open items. Fix attempted, not merged.
The short answer
1open issue
2open PRs
6items grouped
- Known?
- Yes. 6 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMultiple bug reports and fix attempts addressing how skills lock files compute or store content hashes, which causes perpetual false 'update_available' signals. Fixes involve bundle_content_hash usage, stable prefix path handling, and consistent sort ordering.
Open issues1
- Issue#41176[Bug]: hermes skills update doesn't refresh lock content_hash, causing permanent false 'update_available'
Open PRs2
3 PRs closed without merging
From the close comments: duplicate 2 · other 1
-
#41204 fix(skills): refresh lock content_hash after update to prevent false 'update_available' (#41176) · duplicate →
#41199 -
#41333 fix(skills): use bundle_content_hash in lock to fix false update_available (#41176) · other →
9dbad19,9ec2a47,a51c739 -
#55629 fix(skills): keep lock hashes stable for prefix paths · duplicate →
#53448,#53877,#53404
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.33: 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
- skills
- Closed issues
- 0
- Attempts
- 3 PRs closed without merging