Skip to content

Tags: ForestHubAI/edge-agents

Tags

go/v1.0.8

Toggle go/v1.0.8's commit message
test(engine-build): cover bindingFor and indexFor binding resolvers

go/v1.0.7

Toggle go/v1.0.7's commit message
fix(engine-backend): correct provider catalog endpoint to /llm/providers

go/v1.0.6

Toggle go/v1.0.6's commit message
chore: regenerate engine bindings after deploymentId description edit

The contract's deploymentId description was shortened but types.gen.go was
not regenerated, drifting the committed Go binding from contract/engine.yaml
and failing the CI drift check. Regenerate to bring them back in sync.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

go/v1.0.5

Toggle go/v1.0.5's commit message
fix: relocate engine memory dir to /var/lib/foresthub/memory

Move the memory working-copy dir from /var/forest to the FHS-standard
/var/lib/foresthub/memory, kept in sync across the Dockerfile, the
engine config default, and the CLI's generated compose.

The Dockerfile now stages the mount point and copies it with nonroot
(65532) ownership so the named engine-memory volume inherits writable
permissions on first use — a distroless nonroot container otherwise
cannot write to a root-owned mount point. Document the volume's
persistence and the bind-mount alternative in the generated README.

go/v1.0.4

Toggle go/v1.0.4's commit message
refactor: rename healthz endpoint to status and update related respon…

…se models

go/v1.0.3

Toggle go/v1.0.3's commit message
refactor: update model capability references and enums across API def…

…initions

go/v1.0.2

Toggle go/v1.0.2's commit message
llmproxy self hosted config wired in

go/v1.0.1

Toggle go/v1.0.1's commit message
repo rename