Skip to content

v0.8.6

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Jul 13:52
· 83 commits to main since this release
v0.8.6
94270f0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Maintenance release: audit-log retention is now actually enforced, three previously-inert config knobs work, and duplicate/vestigial API endpoints are removed.

Highlights

  • Audit-log retention is now enforced — a background sweep prunes audit_logs rows past core.api.config.audit.retention_days (default 90) in batches, electing a single pruner across replicas. Previously the retention window was advisory and expired rows accumulated forever. Set retention_days: 0 to keep audit rows indefinitely.
  • audit.api_audit_enabled is now settable via Helm — the key was fully wired in Python but unreachable from values.yaml / the rendered ConfigMap.

Bug Fixes

  • Make audit retention, api_audit_enabled, and the proxy HPA memory knob real (#207)

Breaking Changes

Three unused, duplicate/vestigial /api/v1 endpoints were removed (no known consumers — the Go CLI/agent/bridge and web UI never called them). If you integrated against them directly:

  • GET /auth/ca/public → use GET /certificates/ca (returns the same CA public cert).
  • POST /agents/{id}/status → agents report status via the heartbeat; there is no separate status call.
  • GET /audit/sessions/{session_id}/recording → use GET /audit/recordings?session_id={id} (list) or GET /audit/recordings/{id} (fetch).

Upgrade Note

Because retention is now enforced, the first sweep after upgrade will delete audit_logs older than retention_days. If you relied on the previous (unenforced) indefinite retention, set retention_days: 0 before upgrading.

Full Changelog: v0.8.5...v0.8.6

Assets 22
Loading