hermes - 💡(How to fix) Fix [bug] pyproject.toml exclude-newer = "7 days" blocks dependency resolution for stable packages [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#19043Fetched 2026-05-03 04:52:44
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×3commented ×2

Root Cause

Actual:

  × Failed to build `hermes-agent @ file:///...`
  ├─▶ Failed to resolve requirements from `build-system.requires`
  ├─▶ No solution found when resolving: `setuptools>=61.0`
  ╰─▶ Because there are no versions of setuptools and you require
      setuptools>=61.0, we can conclude that your requirements are unsatisfiable.
      hint: `setuptools` was filtered by `exclude-newer` to only include
      packages uploaded before 2026-04-26T...

Code Example

cd hermes-agent
# With exclude-newer = "7 days" in pyproject.toml
uv pip install -e ".[all]"

---

× Failed to build `hermes-agent @ file:///...`
  ├─▶ Failed to resolve requirements from `build-system.requires`
  ├─▶ No solution found when resolving: `setuptools>=61.0`
  ╰─▶ Because there are no versions of setuptools and you require
      setuptools>=61.0, we can conclude that your requirements are unsatisfiable.
      hint: `setuptools` was filtered by `exclude-newer` to only include
      packages uploaded before 2026-04-26T...

---

× No solution found when resolving dependencies:
  ╰─▶ Because there are no versions of vercel and hermes-agent[all]==0.12.0
      depends on vercel>=0.5.7,<0.6.0, we can conclude that
      hermes-agent[all]==0.12.0 cannot be used.

---

[tool.uv]
# Option 1: Remove entirely (recommended — pyproject lock files or requirements.txt handle reproducibility)
# Option 2: Scope to specific packages only
exclude-newer-package = ["some-package=false"]
RAW_BUFFERClick to expand / collapse

Describe the bug

The exclude-newer = "7 days" setting in [tool.uv] (pyproject.toml, line 176) causes uv pip install to fail when resolving dependencies for packages that haven't had a release within the last 7 days. This affects both the build system (setuptools>=61.0) and optional extras (vercel>=0.5.7,<0.6.0).

Since hermes update runs uv pip install -e ".[all]" (or falls back to individual extras) after pulling new commits, this setting silently blocks dependency updates whenever the PyPI upload window excludes critical packages.

To Reproduce

cd hermes-agent
# With exclude-newer = "7 days" in pyproject.toml
uv pip install -e ".[all]"

Expected: All dependencies resolve and install successfully.

Actual:

  × Failed to build `hermes-agent @ file:///...`
  ├─▶ Failed to resolve requirements from `build-system.requires`
  ├─▶ No solution found when resolving: `setuptools>=61.0`
  ╰─▶ Because there are no versions of setuptools and you require
      setuptools>=61.0, we can conclude that your requirements are unsatisfiable.
      hint: `setuptools` was filtered by `exclude-newer` to only include
      packages uploaded before 2026-04-26T...

Same failure for the vercel extra:

  × No solution found when resolving dependencies:
  ╰─▶ Because there are no versions of vercel and hermes-agent[all]==0.12.0
      depends on vercel>=0.5.7,<0.6.0, we can conclude that
      hermes-agent[all]==0.12.0 cannot be used.

Environment

  • Hermes Agent: v0.12.0 (2026.4.30)
  • Python: 3.11.15
  • uv: 0.11.6
  • OS: Linux (Debian-based)

Suggested fix

Remove exclude-newer = "7 days" from [tool.uv] in pyproject.toml, or use exclude-newer-package to target only specific packages if reproducibility is the concern:

[tool.uv]
# Option 1: Remove entirely (recommended — pyproject lock files or requirements.txt handle reproducibility)
# Option 2: Scope to specific packages only
exclude-newer-package = ["some-package=false"]

Impact

Any user running hermes update when there are new commits will hit this dependency resolution failure during the "Updating Python dependencies..." step. The update appears to succeed on the git side ("Already up to date" when no new commits), but silent dependency failures leave the environment with stale or broken packages.

extent analysis

TL;DR

Remove the exclude-newer = "7 days" setting from [tool.uv] in pyproject.toml to resolve the dependency resolution failure.

Guidance

  • The exclude-newer setting is causing the issue by filtering out packages that haven't had a release within the last 7 days, including critical dependencies like setuptools and vercel.
  • To verify the fix, run uv pip install -e ".[all]" after removing the exclude-newer setting and check that all dependencies resolve and install successfully.
  • If reproducibility is a concern, consider using exclude-newer-package to target specific packages instead of removing the setting entirely.
  • Be aware that removing the exclude-newer setting may introduce reproducibility issues if not managed through other means, such as pyproject lock files or requirements.txt.

Example

[tool.uv]
# Remove the exclude-newer setting
# exclude-newer = "7 days"

Alternatively, scope the exclude-newer setting to specific packages:

[tool.uv]
exclude-newer-package = ["some-package=false"]

Notes

The suggested fix assumes that the exclude-newer setting is not necessary for the project's reproducibility requirements. If reproducibility is a concern, additional measures should be taken to ensure consistent dependency resolution.

Recommendation

Apply the workaround by removing the exclude-newer setting, as it is the most straightforward solution to resolve the dependency resolution failure. This is recommended because the issue is caused by the exclude-newer setting, and removing it will allow the dependencies to resolve correctly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [bug] pyproject.toml exclude-newer = "7 days" blocks dependency resolution for stable packages [2 comments, 2 participants]