Fixed
Full Changelog: https://github.com/giantswarm/muster/compare/v5.40.0...v5.40.1
Full Changelog: https://github.com/giantswarm/muster/compare/v5.40.0...v5.40.1
spec.progress.maxDuration. On a tool call whose caller sent a progressToken, every progress notification from the server now restarts spec.timeout, up to the new MCPServer field progress.maxDuration (seconds, from timeout to 3600, default 3600); a call cut at that bound fails with no answer within the server's progress.maxDuration of …. Setting it equal to timeout turns the extension off for a server. Every other call and operation keeps spec.timeout as its whole budget. (giantswarm/roadmap#4394)llmRouting.rateLimits and llmRouting.external.rateLimits: token and request rate limits on the LLM endpoint (giantswarm/giantswarm#38004). Each entry is one item of an AgentgatewayPolicy’s traffic.rateLimit.local: tokens or requests per unit, optional burst, and optional key, a CEL expression through tpl giving each distinct value its own bucket. agent-platform-connectivity-llm-rate-limit targets the data-plane Gateway’s llm listener, agent-platform-connectivity-llm-external-rate-limit the external route; empty (the default) renders neither. values.yaml shows a per-agent key, read from the kagent identity headers only behind the Substrate egress predicate, and a per-API-key one (apiKey.name). Buckets are kept per data-plane replica. Needs components.agentgateway.versionRange at 2.8.0 or later, whose CRD carries key. make verify-llm-rate-limit asserts the renders, the schema and both policies against the floor CRD.Full Changelog: https://github.com/giantswarm/agent-platform/compare/v4.128.0...v4.129.0
Full Changelog: https://github.com/giantswarm/klaus-toolchains/compare/go/v0.1.28...go/v0.1.29
components.workspace-manager.versionRange is >=0.5.0 <1.0.0 (was >=0.4.0 <1.0.0), and the customer BOM pins workspace-manager 0.5.0: the provider kind gitlab (giantswarm/workspace-manager#54). A workspace-manager.providers[] instance of kind gitlab connects a person’s GitLab account (gitlab.com or a self-managed GitLab, CE or EE) through an OAuth application with the scopes api read_user read_repository write_repository, and syncs a workspace’s mirrors with a group access token (read_api, read_repository); its values are url, apiURL (default <url>/api/v4), token and oauth.clientID/oauth.clientSecret, credentials as Secret references only, and the connectivity chart opens the manager’s egress to its hosts. An earlier manager refuses the kind at start, so a gitlab instance under a range whose floor is below 0.5.0 fails the render naming the floor (agent-platform.workspaceManager.gitlabFloor; a release candidate of it counts too). The chart takes no new value, so the release rolls in place. make verify-workspace-manager.Full Changelog: https://github.com/giantswarm/muster/compare/v5.39.5...v5.39.6
Full Changelog: https://github.com/giantswarm/klaus/compare/v1.0.1...v1.0.2
Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.5.3...v0.5.4
Full Changelog: https://github.com/giantswarm/klaus-toolchains/compare/go/v0.1.27...go/v0.1.28