Skip to content

AgentHealth v0.7.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Oct 05:56
· 56 commits to main since this release
v0.7.0
b619fd2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

AgentHealth v0.7.0 — Agent Router integration

v0.7.0 implements Phase 9 with a vendor-neutral router target for explicitly
configured read-only HTTP signals. See PR #24,
RFC #23 and the
impact review.

Changes

  • Add router support to ping, check and doctor, retaining terminal, JSON
    and YAML output and the existing health exit codes.
  • Add router to configuration/result type schemas and allow HTTP expectations
    on top-level router targets and nested dependencies.
  • Use GET for read-only router signals, retaining HTTP/API HEAD and gateway GET.
  • Preserve named router, direct-backend and routed-path results independently,
    including critical failure propagation and optional dependency degradation.
  • Reuse bearer environment references, verified TLS, redirect rejection,
    deadlines and bounded response matching. Functional probes require explicit
    opt-in and never retry; reachability/authentication preflight GETs mean every
    configured probe endpoint must be read-only.
  • Add failure-isolation, aggregation, functional-bound and CLI tests; schema
    fixtures; a direct-agent/router/backend/path example; and phase documentation.

Compatibility and migration

This additive release retains configuration/result v1, existing result structure,
health states and exit codes. Existing supported checks keep their behavior.
Older binaries reject the new router type; upgrade before using router targets.
Configure actual health signals and each routed endpoint explicitly. Credentials,
checks and dependency policies are not inherited. A healthy router signal does
not establish backend or path health, and a failed route alone cannot identify
its cause. Aggregate status includes dependency results.

Installation

Download the matching archive and SBOM from the v0.7.0 release,
verify checksums.txt, signed provenance and SBOM attestations using the
installation guide, for the v0.7.0 download commands. Archives cover Linux AMD64/ARM64,
macOS AMD64/ARM64 and Windows AMD64, with five matching CycloneDX SBOMs.

agenthealth version
agenthealth ping router http://localhost:8081/ready
agenthealth doctor examples/router-check/agenthealth.yaml

The endpoint and example require your running services. Adjust them to match
your deployment; sample ports/paths are not product defaults. See the
router guide and example setup.

Limitations

This generic HTTP interface integration does not certify a router product or
version. No admin inventory, inferred endpoints, discovery, failover probes,
model generation or arbitrary mutations are supported. HTTP/MCP/A2A paths use
their existing adapters. External CLI route probes do not prove communication
from the direct agent runtime; Phase 7 safe downstream handlers remain required.
Shared graph identity, AHP serving, SDK packages, Docker and Kubernetes remain
future work. Real product interoperability remains Phase 25 work. OS-native
signing and macOS notarization are not provided.

Validation

Phase 9 implementation CI passed all nine checks, including Linux/macOS/Windows
Go race tests, current/legacy official SDK interoperability, vulnerability scanning,
schemas and documentation. The implementation review recommended approval with
zero findings; a non-blocking result-fixture suggestion was addressed separately.
Local Go vet/race tests passed with Go 1.26.0. Python tests with Go on PATH reported
88 passed and three optional SDK tests skipped; those SDK suites passed in CI.
The release workflow uses Go 1.27.1 and smoke-tests Linux AMD64. Other archives
are cross-compiled, without local runtime validation on other platforms.

Assets 13
Loading