components.<name>.omitKeys, the keys dropped from a component’s forwarded values block. It exists for a block that holds a key belonging to this umbrella rather than to the component’s chart, where that chart validates values with additionalProperties: false and would reject it.Full Changelog: https://github.com/giantswarm/muster/compare/v5.6.1...v5.6.2
Full Changelog: https://github.com/giantswarm/muster/compare/v5.6.0...v5.6.1
Full Changelog: https://github.com/giantswarm/muster/compare/v5.5.6...v5.6.0
retry block (count, delay, backoff_multiplier) is now rejected at load time, with a message pointing at expected.wait_for_state. It was declared on TestStep and range checked by the loader, and nothing else ever read it — so a step declaring retry got exactly one attempt while reading as if it polled, and TestStepResult.RetryCount (printed by the reporter) was always zero. The three steps in the dex-token-forward scenario that used it to poll for eventually-consistent state — backend registration, the OBO reconnect, and the forwarded-token assertion — were therefore flake-prone in precisely the place their author had covered; they now use wait_for_state, which is the mechanism that works. RetryConfig and RetryCount are removed. A new test asserts that every field of TestStep names the file that acts on it, and fails the build when a field is declared and validated but never honoured — the same class of bug as #1038, one level up from expectation kinds.wait_for_state on an MCP tool step no longer discards a first response that already satisfies the step’s expectations. The polling loop ignored the response its caller had just obtained and judged the step only from the first tick onward, so every such step paid a mandatory poll interval, and a step was failed outright when re-invoking the tool did not return the same answer — reported against the first, passing response, so the output showed a satisfied payload on a failed step. Steps whose invocation is the assertion (a token-forwarding call, anything not idempotent) were the ones at risk. The test_* path already judged the first response; the two now agree, which is the parity TestEveryExpectationKindIsEnforcedOnBothStepKinds exists to defend. dex-token-forward drops from 2.5s to 0.5s as a result.Full Changelog: https://github.com/giantswarm/muster/compare/v5.5.4...v5.5.5
forwardToken: true that registers after muster starts now reaches the next login, so the forwarded ID token carries the audience its backend expects. Existing sessions are not repaired: affected users must log in again once. A background refresher re-reads the set every 10 seconds, so no login costs an MCPServer list call, and a read that fails serves the last known set instead of an empty one.dex_audiences_changed security audit event, alongside a log line. The set comes from MCPServer requiredAudiences and now changes without a muster restart.core_mcpserver_list now reports a failure when the MCPServer definitions cannot be read, auto-start reports the failure instead of starting no servers silently, and periodic resync logs it instead of treating it as “no MCPServers exist”.Full Changelog: https://github.com/giantswarm/muster/compare/v5.5.2...v5.5.3
Full Changelog: https://github.com/giantswarm/muster/compare/v5.5.1...v5.5.2
Full Changelog: https://github.com/giantswarm/muster/compare/v5.5.0...v5.5.1