Changed
- Align files according to platform standards in #371 by @giantswarm-align-files[bot]
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.238...v0.0.239
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.238...v0.0.239
Full Changelog: https://github.com/giantswarm/muster/compare/v0.18.7...v0.18.8
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.237...v0.0.238
Full Changelog: https://github.com/giantswarm/klaus-oci/compare/v0.0.56...v0.0.57
sub=human, act=agent) re-presented at the front door is signature-validated with no token-store entry, so it previously carried no session ID; backend tools that require session auth then rejected it and the connection fell back to the agent ServiceAccount. Bumping mcp-oauth to v0.18.0 makes the ValidateToken middleware assign a session to every validated token (FamilyID when present, else the deterministic bearer-derived ID), so the existing session lookup resolves the OBO bearer and the per-backend localMint runs as the human. No muster code change.Full Changelog: https://github.com/giantswarm/agentic-platform/compare/v1.15.4...v1.16.0
agents.definitions.sre-agent: list muster’s meta-tools explicitly under toolNames (was empty = all) so the kagent Agent Details UI renders them by name instead of a single “Unknown Tool” entry. The agent’s available tools are unchanged — backend tools (x_kubernetes_*, x_prometheus_*, workflows) are still reached through call_tool. Applied to both the umbrella agentic-platform and agentic-platform-connectivity values.yaml (kept in sync).Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.236...v0.0.237
Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.110...v0.0.111