fix: include messaging dependency group in default Hermes build #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/add-discord-py"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What this fixes
Adds
discord.py,python-telegram-bot,slack-bolt, and other messaging platform libraries to the default Hermes derivation. Also adds adocker-imageOCI image target for k3s deployment.Fixes https://os.scoble.me/forgejo/sscoble/hermes-speckl/issues/2
Problem
The
[all]extras group in upstream hermes-agent (NousResearch) stopped including themessagingdependency group on 2026-05-12 — it switched to lazy-install at runtime. But our Nix-built container images running on k3s have nopipavailable, so lazy installation fails.Agent logs show:
Changes
extraDependencyGroups = ["messaging"]override on the hermes-agent derivationdocker-imageOCI image target built withdockerTools.buildLayeredImageforAllSystemsmoved intolet...inbinding for flake-parts compatibilityflake.lock(previously missing)After Merge
Verified: The image builds successfully and includes
discord.py==2.7.1,python-telegram-bot==22.6, andslack-bolt==1.27.0. Image imported to containerd and ready for deployment.@ -0,0 +1 @@/nix/store/wmr5qjizys6dsbsrgvydc0c7ijx4inra-hermes-agent-0.13.0this should be .gitignored
Changes requested → addressed:
resultsymlink)nix build .#docker-imagenot.#default)flake.lockto the repo (was previously missing, causing eval issues)forAllSystemsscoping — moved intolet...inbinding for flake-parts compatibilityThe image has been verified: builds successfully, discord.py/slack-bolt/telegram-bot all import cleanly. Image imported to containerd and ready for deployment once merged.