NousResearch/hermes-agent

uv exclude-newer handling for exact pins and mirrors

Cluster 132558 · hermes cli. Data as of 2026-10-27 11:58 UTC

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

open issues

open PRs

items grouped

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

Next step: read #137110, then check it covers your case.

Read #137110 Pick up a Lab task

These members appear to concern how a release-age quarantine (uv exclude-newer) interacts with exact package pins and package indexes or mirrors lacking upload-time metadata. One title mentions moving the age check to lock time, another mentions exempting exact pins, and a third reports resolution problems for specific packages; their outcomes are not established here.

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.

#137110 Plugin installs work on any package mirror: release age is checked when Hermes locks (3 days), not on users' machines (#135589)

merged to main

files: plugin-catalog/README.md, pm/AGENTS.md, pm/environment.py, pm/workspace.py, pyproject.toml, tests/pm/test_workspace.py, tests/pm/test_workspace_build_inputs.py, tests/test_packaging_metadata.py, website/docs/developer-guide/plugins/catalog-submission.md, website/docs/developer-guide/plugins/index.md, website/docs/reference/package-management.md

1 PR closed without merging

From the close comments: done elsewhere 1

#132574 fix(pm): exempt every exact pin from the uv exclude-newer quarantine · done elsewhere → 37725f2, #137110

Closed issues · 1

Closed#132558exclude-newer-package omits exact pins, bricking resolution on indexes without PEP 691 upload-time (pilk/silk)

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

Subsystem: hermes cli
Merged PRs: #137110
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 12 Oct 2026

For your agent

The same facts, typed.

cluster/132558.json
cluster/132558.md