🚀 Kargo v1.12.6 is here! v1.12 is the last release line before Kargo 2.0, so this patch carries a few improvements that would ordinarily have waited for a minor release: stricter Warehouse validation, a new tar step option, a round of fixes, and some welcome relief for large installations.
⚠️ Heads Up: Stricter Warehouse Validation
-
Warehouse Subscriptions Now Reject Unknown Fields (#7925): A subscription field that didn't belong to the subscription's type used to be accepted and then silently ignored. The easiest way to hit this was the constraint field, whose name depends on the subscription type: image subscriptions use
constraint, while chart and Git subscriptions usesemverConstraint. Use the wrong one and the subscription behaved as though it had no constraint at all. The Warehouse webhook now validates each subscription against its type's schema and rejects unknown fields and invalid values. This affects only configuration that was already wrong. Valid Warehouses behave exactly as before; the only difference is that a mistake that used to be silently ignored is now loudly rejected, which is the better outcome.Existing Warehouses keep running after the upgrade, and metadata-only updates, such as refreshes, still go through. The next change to an affected Warehouse's spec, however, is rejected until the offending field is fixed. If you manage Warehouses with a GitOps agent, look for failed syncs. Keep in mind that correcting a misnamed constraint applies it for the first time, so the Warehouse may discover a different set of artifacts than before. See Working with Warehouses.
➡️ Promotion Improvements
- Fixed File Modes in
tarArchives (#7770): Files rendered during a promotion may be owner-only (0600/0700), which a non-root container can't read after extracting the archive (from an image volume, for instance). Thetarstep's newfileModeanddirModeoptions record a fixed mode for every regular file and directory in the archive. (docs)
🐛 Notable Bug Fixes
-
No More Failed Logins Before Every Git Operation (#8011): With a username and password configured for an HTTPS Git repository, every Git operation first tried the username with an empty password. Authentication always succeeded on the next attempt, but Git servers that track failed logins counted one against the account for every Warehouse poll and every Git promotion step.
-
argocd-updateNo Longer Requests the Same Sync Twice (#7981): If the step ran again before Argo CD had started the sync it requested, it requested that sync a second time, which could make Argo CD start the sync over. The step now waits for the sync it already asked for. -
No More Duplicate Verifications (#7825): Once a Stage had been reverified, later promotions to it could start two verification
AnalysisRuns for the same Freight, milliseconds apart. When the two runs shared state, such as a test account, they could fail each other and leave the Freight unverified. -
httpStep Honors Its Failure Criteria (#7926): When an error response didn't have the shapesuccessExpressionexpected, the step errored without ever checkingfailureExpression. Failure criteria are now checked first, so the step fails with yourerrorExpressionmessage, as documented. -
Integer Outputs from Parse Steps (#7897): A
yaml-parse,json-parse, ortoml-parseoutput whose expression returned an integer, such aslen(items), made the next step error withcannot deep copy int. -
UI Freeze on Fan-Out/Fan-In Pipelines (#7836): Stacking a node in a pipeline with repeated fan-out/fan-in layers could hang the browser tab on every load.
-
Login Redirects Under a Base Path (#7877): With
api.basePathset, logging in redirected to a URL with the base path doubled. -
Rapid Refreshes (#7933): A second refresh of the same resource within the same second was silently dropped.
⚡ Performance at Scale
-
Warehouses Stop Re-Creating Existing Freight (#7847): Every Warehouse poll re-submitted its latest Freight even when it already existed, costing a rejected API write and a round of admission webhook calls each time. Those writes are gone, and
status.lastFreightIDnow names Freight that actually exists. -
Fewer Freight Status Writes (#7904): A promotion now updates the Freight's status once instead of twice, easing contention on the API server when many Stages share the same Freight.
-
A Quieter Project Controller (#7741): The Project controller no longer reconciles in response to its own status updates. In testing, this cut the management controller's memory allocations by about 30%.
🔒 Security
github.com/go-jose/go-jose/v4is upgraded to v4.1.9, which addresses GHSA-mgcc-cww5-fp2q and several other advisories. (#7990)
🙏 Special Thanks
Thank you to community members who made their first contributions in this release!
Full Changelog: v1.12.5...v1.12.6