NousResearch/hermes-agent

Desktop build freshness and stamp pipeline fixes

Cluster 123308 · other. Data as of

Nothing open on GitHub. Fix merged in #127237 on 1 Oct 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #127237. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #127237. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address bugs in the desktop build system related to hashing, identity vs. clock-based stamping, input change detection, and race conditions that disrupt the freshness pipeline. The fixes target how build inputs are named, hashed, and checked for staleness.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #127237 fix(build,update): OS metadata, stamp-clock races and stacked completions break the desktop freshness pipeline

    merged to main

    files: apps/desktop/scripts/bundle-electron-main.mjs, hermes_cli/source_completion.py, scripts/build/README.md, scripts/build/desktop.mjs, scripts/build/freshness.mjs, scripts/build/frontend-common.mjs, tests-js/desktop-builder.test.mjs, tests-js/freshness-metadata.test.mjs, tests-js/frontend-common.test.mjs, tests-js/product-builders.test.mjs, tests/hermes_cli/test_source_completion_stamp.py, tests/hermes_cli/test_update_completion_process.py

2 PRs closed without merging

From the close comments: partial fix 1 · other 1

  • #123377 fix(build): hash the desktop stamp's identity, not its build clock (#123308) · partial fix → f17856d, e8cf816, #1, #2, #96581, #123376
  • #127192 fix(build): name the inputs that changed when a product build is refused · other → #127237, #122632
Closed issues · 1
  • Closed#123308fix(build): desktop build rewrites a hashed prepared input, so freshness.mjs trips on the build's own change and the caller never retries
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.50: the share of item 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.

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 Lab

At a glance

Subsystem
other
Merged PRs
#127237
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
1 Oct 2026

For your agent

The same facts, typed.