Changed
- (deps) Update dependency @anthropic-ai/claude-code to v2.1.261 in #455 by @renovate[bot]
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.322...v0.0.323
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.322...v0.0.323
Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.148...v0.0.149
Full Changelog: https://github.com/giantswarm/muster/compare/v5.9.3...v5.9.4
Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.147...v0.0.148
Full Changelog: https://github.com/giantswarm/klaus-oci/compare/v0.0.70...v0.0.71
Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.2.55...v0.2.56
Full Changelog: https://github.com/giantswarm/klaus/compare/v0.0.321...v0.0.322
Full Changelog: https://github.com/giantswarm/agent-platform/compare/v3.7.1...v3.7.2
muster test no longer terminates the instances of another muster test running at the same time. The start-up sweep for instances left behind by an earlier run matched every muster serve --config-path .../muster-test-... process on the machine and sent each one SIGTERM, so a second suite started in another terminal – or the harness’s own unit tests under go test ./internal/testing/, which called the sweep for real – killed the first suite’s instances: scenarios then failed with muster instance process exited (code 0) before becoming ready, or an instance shut down cleanly mid-scenario. The sweep now terminates only instances whose parent muster test process is gone (re-parented after a crash or kill), which is the case it exists for; instances of a live harness are left alone, and the unit tests run the sweep against a fabricated process table plus two stand-in processes of their own.Full Changelog: https://github.com/giantswarm/muster/compare/v5.9.1...v5.9.2