Changes and Releases

Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.

• May 11, 2026 AI Agents klaus v0.0.149

  What’s Changed

  • chore(deps): bump Go to 1.26.3 and golang.org/x/net to v0.53.0 by @teemow in https://github.com/giantswarm/klaus/pull/253

  Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.148...v0.0.149

• May 11, 2026 AI Agents muster v0.1.159

  What’s Changed

  • test(ats): tighten smoke-test timeout and rerun budget by @teemow in https://github.com/giantswarm/muster/pull/655

  Full Changelog: https://github.com/giantswarm/muster/compare/v0.1.158...v0.1.159

• May 11, 2026 AI Agents klausctl v0.0.79

  What’s Changed

  • chore(deps): update go toolchain directive to v1.26.3 by @renovate[bot] in https://github.com/giantswarm/klausctl/pull/217

  Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.0.78...v0.0.79

• May 11, 2026 AI Agents muster v0.1.158

  What’s Changed

  • fix(deps): update module github.com/giantswarm/mcp-oauth to v0.2.119 by @renovate[bot] in https://github.com/giantswarm/muster/pull/645

  Full Changelog: https://github.com/giantswarm/muster/compare/v0.1.157...v0.1.158

• May 11, 2026 AI Agents klausctl v0.0.78

  What’s Changed

  • fix(deps): update module github.com/mark3labs/mcp-go to v0.52.0 by @renovate[bot] in https://github.com/giantswarm/klausctl/pull/219

  Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.0.77...v0.0.78

• May 11, 2026 AI Agents klausctl v0.0.77

  What’s Changed

  • chore(deps): update dependency architect to v8 by @renovate[bot] in https://github.com/giantswarm/klausctl/pull/220

  Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.0.76...v0.0.77

• May 11, 2026 AI Agents klausctl v0.0.76

  What’s Changed

  • fix(deps): update module github.com/giantswarm/klaus-oci to v0.0.24 by @renovate[bot] in https://github.com/giantswarm/klausctl/pull/218

  Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.0.75...v0.0.76

• May 10, 2026 Developer Portal backstage v0.129.3

  Fixed

  • Stabilise the AI chat transport across React renders. useChatSetup constructed a fresh AssistantChatTransport on every render and handed it to useChatRuntime; when its identity changed mid-stream (e.g. as a side effect of a state update triggered by streamed reasoning-delta / tool-input-delta events), the runtime tore down the in-flight chat fetch with TypeError: network error. Envoy logged the symptom as response_flags: DC (downstream remote disconnect) against a healthy Backstage upstream while the SSE stream summary was sawFinish=false, last event tool-input-delta, surfacing in the UI as a “Network error” banner even though no real network outage occurred. The transport is now memoised on the resolved API URL and the stable getHeaders / debugFetch callbacks, so a single transport lives for the component’s lifetime.
  • AI chat instrumentation: observe the caller’s AbortSignal and log abort events with the reason inline (ABORT signaled by client at <ms> -- reason: <name>: <message>). Stream-outcome lines now annotate aborted streams with [client-aborted at Nms reason="..."] so a “Network error” banner can be classified as a deliberate client cancel (transport rebuild, unmount, manual stop) versus a real proxy / network failure (no abort signal fired, raw stream error). Read errors that fired after the caller aborted are now logged as console.warn (“cancelled by client AbortSignal”) rather than console.error (“STREAM READ FAILED”), reserving the latter for the genuine pre-finish, non-aborted failure mode.

  See ./docs/releases/v0.129.3-changelog.md for more information.

• May 10, 2026 Developer Portal backstage v0.129.2

  Fixed

  • AI chat instrumentation: render the SSE stream summary inline in the log message (bytes=... events=... sawFinish=... lastEventType=...) instead of attaching it as a trailing object argument, so it stays readable in browser-console consumers that flatten the args array (devtools-snapshotters, log shippers, the Cursor IDE browser, etc.) rather than collapsing to “[object Object]”. Also classify a stream read error that arrives after a finish event was already parsed as a post-completion teardown (console.warn, message already committed) instead of a network failure (console.error); this matches the actual semantics of the AI SDK aborting the underlying fetch once it has finished consuming the stream. See ./docs/releases/v0.129.2-changelog.md for more information.
• May 10, 2026 Developer Portal backstage v0.129.1

  Fixed

  • AI chat: always log network-level diagnostics (request URL, response status / headers, fetch errors, SSE stream lifecycle including premature termination) to the browser console so a “Network error” banner can be triaged from a user report without requiring the ai-chat-verbose-debugging feature flag. Verbose payload-level logging (messages, system prompt, tool schemas, per-event SSE detail) remains gated on the feature flag in non-production builds. See ./docs/releases/v0.129.1-changelog.md for more information.

• Newer entries
• Older entries