platformchangelog.dev
44 tools
feedrelease

Kargo v1.12.6

security+~~~********!

Kargo v1.12.6 was released with 17 changes, including a security upgrade of go-jose to v4.1.9 that addresses GHSA-mgcc-cww5-fp2q and several other advisories. Fixes cover tar archive file modes (new fileMode and dirMode options), redundant Freight re-creation and status writes, a spurious failed-login on every HTTPS Git operation, duplicate Argo CD sync requests, and duplicate verifications. Warehouse subscriptions now reject unknown fields via the webhook.

What changes for platform teams

Platform teams running Kargo get fewer API server writes and webhook calls, fewer failed logins against Git servers, and no duplicate Argo CD syncs or verification runs. Warehouse configurations with misspelled or wrong-type fields such as constraint versus semverConstraint will now be rejected at admission rather than silently ignored, so check existing configs before upgrading.

Changes

  • Github.com/go-jose/go-jose/v4 is upgraded to v4.1.9, which addresses GHSA-mgcc-cww5-fp2q and several other advisories.security
  • 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.lastFreightID now names Freight that actually exists.changed
  • 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.changed
  • 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%.changed
  • Fixed File Modes in tar Archives (#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). The tar step's new fileMode and dirMode options record a fixed mode for every regular file and directory in the archive. (docs)added
  • 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.fixed
  • Argocd-update No 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.fixed
  • No More Duplicate Verifications (#7825): Once a Stage had been reverified, later promotions to it could start two verification AnalysisRun s 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.fixed
  • Http Step Honors Its Failure Criteria (#7926): When an error response didn't have the shape successExpression expected, the step errored without ever checking failureExpression. Failure criteria are now checked first, so the step fails with your errorExpression message, as documented.fixed
  • Integer Outputs from Parse Steps (#7897): A yaml-parse, json-parse, or toml-parse output whose expression returned an integer, such as len(items), made the next step error with cannot deep copy int.fixed
  • 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.fixed
  • Login Redirects Under a Base Path (#7877): With api.basePath set, logging in redirected to a URL with the base path doubled.fixed
5 more lines
  • Rapid Refreshes (#7933): A second refresh of the same resource within the same second was silently dropped.fixed
  • 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 use semverConstraint. 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.other
  • @lofonehother
  • @mattkrickother
  • @n2p5other
17 lines1 security1 added3 changed8 fixed4 othertyped from the source notes

Full release notes ↗ · all Kargo releases

written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Report a mistake

context

Tools

Kargo

Other Kargo releases

How this was written

The change list is the project's own release notes, sorted into change types by fixed rules. The summary was written from the original by the model named above, checked by fixed publishing rules, and read by an editor after publication. See the methodology.

Back to the feed

Kargo v1.12.6 release notes | Platform Changelog