🐛 Kargo v1.10.6 is a patch release gathering four bug fixes, including a regression from v1.10.5 that prevented project Roles from loading in the UI.
🐛 Bug Fixes
-
promotiontasksresource rejected when viewing project Roles (#6432): After upgrading to v1.10.5, opening the Roles view for any project in the UI failed witherror normalizing RBAC policy rules: unrecognized resource type "promotiontasks". v1.10.5 addedPromotionTaskpermissions to the project admin role, but the API server's RBAC validation allowlist was not updated to match. The resource name is now recognized, restoring the Roles view. -
ECR credential provider no longer shadows other providers (#6377): When the controller was configured with IRSA or EKS Pod Identity, the ECR (managed identity) credential provider reported that it supported every image and Helm URL — not just ECR URLs. Because the credential registry stops at the first matching provider, this prevented other providers (such as Google Artifact Registry) from ever being reached. The ECR provider is now selected only when the repository URL matches the expected ECR format, so mixed multi-cloud credential setups work as expected.
-
Commits that only move or rename files are now discovered (#6396): When a Git commit moved or renamed files within a Warehouse's subscribed paths without otherwise changing them, Kargo failed to discover the commit and create Freight. Such commits are now detected correctly.
-
Clearer error when resource creation conflicts (#6428): Creating a resource that conflicts with an existing one — for example, recreating a Project whose namespace is still terminating — previously surfaced an opaque, empty
500error. These409 Conflictresponses are now parsed and presented with a meaningful message in the CLI and UI.
Full Changelog: v1.10.5...v1.10.6