chore: add changelog entries for CLI v2.39.0–v2.39.2

[mintlify]

Summary

Adds the changelog entry for CLI v2.39.2, plus the Docker image version fix from v2.39.0 that was missing.

Rebased on main after #376 merged. #376 had already documented v2.39.0 and v2.39.1, so this PR is now purely additive — no deletions.

Conflict resolution

Four conflicts in changelog/index.mdx, resolved as follows:

• v2.39.2 — new, kept as generated. Placed above the August 31 Platform entry, keeping the file newest-first.
• v2.39.0 and v2.39.1 prose — kept the versions already on main from chore: update changelog CLI v2.39.0/v2.39.1 and Platform updates #376 and discarded this branch's rewordings, since they had been through review and use the correct command name (see below).
• The August 24–28 Platform entries — kept main's; this branch predated them.

The Docker version fix

This branch carried a Docker version bullet on both v2.39.0 and v2.39.1, and main had neither. Checking upstream, only one of them is a user-facing fix:

• v2.39.0 (cli#1137) — the real fix. Published images identified themselves as dev+<sha> instead of their release tag, so kosli version in a container could not name the release. Two causes in the Docker build path, both silent. Any image published before v2.39.0 is affected. Kept, reworded around that symptom.
• v2.39.1 (cli#1140) — not a user-facing fix. It resolves the version once in the workflow instead of via git describe in the build, superseding cli#1137's fetch-tags approach, and fixes a smoke-test flake when a release tag is cut at the same commit as an in-flight main pipeline. Its own description says images "report what they did before … except the racy case". Dropped as an internal build change.

That also removes the problem of two consecutive releases each claiming to fix the image version with different causes.

Both bullets appeared only in the releases' "What's Changed" lists rather than their curated sections, which is likely why the first pass missed them.

One correction worth noting

This branch described the v2.39.1 help-text change as affecting kosli snapshot azure-apps. That name comes from the upstream release note, but the command is kosli snapshot azure — the generated reference page is client_reference/kosli_snapshot_azure.md and there is no azure-apps page. main's wording is correct and links the reference; that is what was kept.

Checks

• mint broken-links — clean apart from the pre-existing /getting_started/service-accounts break in tutorials/working_with_controls.mdx, which is on main and untouched here.
• <Update> open/close tags balance at 117 each; no empty headings; entries remain in newest-first date order.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
kosli	🟢 Ready	View Preview	Sep 7, 2026, 9:12 AM

[claude]

Claude finished @dangrondahl's task in 1m 58s —— View job

---

Doc quality review — re-review at bc58f09

• Read changelog/index.mdx at branch head
• Re-check the two findings from earlier rounds
• Verify the v2.39.2 entry against the generated CLI reference
• Structural and link checks

No findings. Nothing in the diff at head clears the reporting bar.

Both earlier findings are resolved:

• kosli snapshot azure-apps — gone; the v2.39.1 entry on main uses kosli snapshot azure with a reference link.
• Competing Docker-version claims — the v2.39.1 bullet is dropped and the v2.39.0 bullet now names one checkable symptom with a version boundary rather than a date.

One thing I checked that wasn't previously verified: the v2.39.2 bullet's substance. 55f14be ("update CLI and helm reference for v2.39.2") touched 18 reference pages, but the only non-sample-data change in the whole release is on client_reference/kosli_attest_sonar.md — overriden → overridden twice in the long description, and overriden/sonar scanner → overridden/Sonar scanner in the --sonar-working-dir row (client_reference/kosli_attest_sonar.md:85). So "corrected typos in the help text for kosli attest sonar and its --sonar-working-dir flag description" is exactly right, and nothing user-facing from that release is missing from the entry. The remaining churn in that commit is regenerated sample data.

Date labels line up with when each release's reference update landed (v2.39.0 → Aug 29, v2.39.1 → Aug 30, v2.39.2 → Sep 1), section order follows the file's New features → Updates → Bug fixes convention, and the 117 <Update> tags balance.
· branch mintlify/0c016c60