NousResearch/hermes-agent

macOS metadata corrupts desktop build freshness checks

Cluster 122632. 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
3items grouped
Known?
Yes. 3 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 issues and fixes concern macOS Finder metadata files (e.g. .DS_Store) interfering with build freshness hashing on desktop, along with related timing and completion pipeline concerns. The work focuses on excluding OS-generated artifacts from freshness detection logic.

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

1 PR closed without merging

From the close comments: done elsewhere 1

  • #122636 fix(build): skip macOS Finder metadata in build freshness hashing (#122632) · done elsewhere → 64eca05, dde4bc7, #122632
Closed issues · 1
  • Closed#122632[Bug]: macOS .DS_Store trips desktop build freshness check, so hermes update never reports success
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.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

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

For your agent

The same facts, typed.