hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 28 Packages Projects Releases Wiki Activity

fix(catalog): re-pin custodian to a commit whose build backend exists

Browse Source 
The previous pin (4474a8d1) declares build-backend
setuptools.backends._legacy:_Backend, which is not importable in any
setuptools release, so uv sync fails before dependency resolution and
the plugin cannot be enabled. d5b4ebf is the upstream fix (one commit
                      ahead, same version 3.0.1) that switches to setuptools.build_meta.

Fixes #124088
This commit is contained in:
Konstantin Khlopkov
2026-09-26 19:34:59 +03:00
committed by Teknium
parent 8822d8be54
commit 3b36a35b86
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
plugin-catalog/custodian.yaml
View File

@@ -1,6 +1,6 @@
name: custodian
repo: https://github.com/indigokarasu/hermes-custodian-plugin
sha: 4474a8d15a37b5343dfa2928eb804b8dad63e765
sha: d5b4ebfd2353a29380a51c8bcba84d4682cf4c91
version: "3.0.1"
description: "Autonomous operations monitor for a Hermes install: scans gateway logs, cron jobs, skill journals and agent data directories, classifies findings against a 27-fingerprint registry, auto-repairs Tier 1 problems, escalates the rest, and keeps an append-only issue ledger. Ships /custodian (status, scan, issues, repair, verify, schedule, confidence, init, escalation-runner), four scan/health tools and a grid dashboard. Disclosure — reads gateway logs, cron job state and per-skill journal files under HERMES_HOME to build its findings, and writes repair actions and an issues ledger back there; it performs no network I/O and holds no credentials. Disclosure — /custodian init registers 3 recurring agent cron jobs (deep scan 4×/day, cron-health 4×/day, escalation runner every 30 min on weekdays)."
maintainer: indigokarasu