Cairn
NousResearch/hermes-agent

Stale certifi CA bundle path after install-environment rotation

Cluster 137255 · agent. Data as of

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

The short answer

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

The members describe one problem: after an install-environment rotation, TLS clients keep using a certifi CA bundle path that points to a deleted directory. One bug report and two pull requests with identical titles propose re-resolving the path; the members do not show whether any fix was merged or works.

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.

  • #140376 fix(ssl): keep TLS working after an install-environment rotation (salvage #137341)

    merged to main

    files: agent/ssl_verify.py, contributors/emails/[redacted:email], hermes_cli/auth_device_flow.py, plugins/browser/_common.py, plugins/model-providers/actual/__init__.py, plugins/platforms/wecom/adapter.py, plugins/platforms/weixin/adapter.py, plugins/web/keenable/provider.py, tests/agent/test_ssl_verify.py, tests/hermes_cli/test_auth_nous_provider.py

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #137256 fix(ssl): re-resolve certifi's CA bundle path after an install-environment rotation · other → 7cc3fb8
  • #137341 fix(ssl): re-resolve certifi's CA bundle path after an install-environment rotation · duplicate → 17724f1, #140376, #137341
Closed issues · 1
  • Closed#137255[Bug]: TLS clients die after an install-environment rotation — certifi's CA bundle path stays in the deleted directory
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 1.00: 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
agent
Merged PRs
#140376
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Oct 2026

For your agent

The same facts, typed.

cluster/137255.json
cluster/137255.md