Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix hermes update downgrades aiohttp from 3.13.4 to 3.13.3

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…

During hermes update, the Python dependency sync downgraded aiohttp from 3.13.4 to 3.13.3.

This may be intentional if the project pins aiohttp==3.13.3, but the update output does not explain why an already newer patch release is being downgraded.

Root Cause

During hermes update, the Python dependency sync downgraded aiohttp from 3.13.4 to 3.13.3.

This may be intentional if the project pins aiohttp==3.13.3, but the update output does not explain why an already newer patch release is being downgraded.

Fix Action

Fix / Workaround

This may be intentional if the project pins aiohttp==3.13.3, but the update output does not explain why an already newer patch release is being downgraded.

If it is not intentional, the dependency constraint should allow the newer compatible patch release.

Code Example

Using Python 3.11.15 environment at: venv
Resolved 100 packages in 223ms
   Building hermes-agent @ file:///home/bitter/.hermes/hermes-agent
      Built hermes-agent @ file:///home/bitter/.hermes/hermes-agent
Prepared 1 package in 906ms
Uninstalled 2 packages in 3ms
Installed 2 packages in 4ms
 - aiohttp==3.13.4
 + aiohttp==3.13.3
 ~ hermes-agent==0.14.0 (from file:///home/bitter/.hermes/hermes-agent)
RAW_BUFFERClick to expand / collapse

Summary

During hermes update, the Python dependency sync downgraded aiohttp from 3.13.4 to 3.13.3.

This may be intentional if the project pins aiohttp==3.13.3, but the update output does not explain why an already newer patch release is being downgraded.

Environment

  • OS: Arch Linux
  • Hermes: Hermes Agent v0.14.0 (2026.5.16)
  • Command invoked by wrapper: hermes update
  • Python environment reported by update: Python 3.11.15 venv
  • Run timestamp: 2026-05-24 23:50 America/Sao_Paulo

Observed output excerpt

Using Python 3.11.15 environment at: venv
Resolved 100 packages in 223ms
   Building hermes-agent @ file:///home/bitter/.hermes/hermes-agent
      Built hermes-agent @ file:///home/bitter/.hermes/hermes-agent
Prepared 1 package in 906ms
Uninstalled 2 packages in 3ms
Installed 2 packages in 4ms
 - aiohttp==3.13.4
 + aiohttp==3.13.3
 ~ hermes-agent==0.14.0 (from file:///home/bitter/.hermes/hermes-agent)

Expected behavior

If aiohttp==3.13.3 is intentionally pinned, the updater should ideally make that clear or document the reason.

If it is not intentional, the dependency constraint should allow the newer compatible patch release.

Impact

The update completed successfully, but the downgrade is surprising in a maintenance/update workflow and can look like a dependency regression.

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…

FAQ

Expected behavior

If aiohttp==3.13.3 is intentionally pinned, the updater should ideally make that clear or document the reason.

If it is not intentional, the dependency constraint should allow the newer compatible patch release.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING