Cairn
NousResearch/hermes-agent

Remove uv exclude-newer restriction from pyproject.toml

Cluster 19043. Data as of

Nothing open on GitHub. Fix merged in #21221 on 7 May 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 #21221. 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
Nothing open on GitHub.

A bug was identified where an exclude-newer date cutoff in pyproject.toml blocked dependency resolution for stable packages. Multiple fix attempts address removing this uv constraint.

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.

  • #21221 fix(install): remove uv exclude-newer cutoff (salvage #19488)

    merged to main

    files: pyproject.toml

    Show the diff
    • pyproject.toml
      @@ -164,6 +164,3 @@ exclude = ["tinker-atropos"]
 [tool.ruff]
 exclude = ["tinker-atropos"]
 select = [] # disable all lints for now, until we've wrangled typechecks a bit more :3
-
-[tool.uv]
-exclude-newer = "7 days"
    • uv.lock
      @@ -8,10 +8,6 @@ resolution-markers = [
     "python_full_version < '3.12'",
 ]
 
-[options]
-exclude-newer = "0001-01-01T00:00:00Z" # This has no effect and is included for backwards compatibility when using relative exclude-newer values.
-exclude-newer-span = "P7D"
-
 [[package]]
 name = "agent-client-protocol"
 version = "0.9.0"

1 PR closed without merging

From the close comments: merged via another change 1

  • #19114 fix(deps): remove exclude-newer from pyproject.toml (fixes #19043) · merged via another change → #19488, #21221
Closed issues · 1
  • Closed#19043[bug] pyproject.toml exclude-newer = "7 days" blocks dependency resolution for stable packages
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
#21221
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
7 May 2026

For your agent

The same facts, typed.

cluster/19043.json
cluster/19043.md