chore: add CLI v2.41.0–v2.43.1 changelog entries - #424
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Claude finished @mbevc1's task in 2m 33s —— View job Doc review
The reference tree is generated from v2.43.1 ( Critical —
|
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
|
|
||
| ## New features | ||
|
|
||
| - **`kosli evaluate policy`** — evaluate a policy and record the decision in a single request, instead of calling evaluate and record separately. |
There was a problem hiding this comment.
Critical — command has no reference page. There is no client_reference/kosli_evaluate_policy.md, and the kosli evaluate group in config/navigation.json:359-363 lists only kosli_evaluate_input, kosli_evaluate_trail and kosli_evaluate_trails. The reference was generated from v2.43.1 (client_reference/overview.md:7), i.e. after the release this entry describes — so if the command existed, its page would be here.
This is also the only new-feature bullet in the PR with no reference link, which fits.
Either the command name is wrong (e.g. it's a flag on an existing kosli evaluate … subcommand), or the command exists upstream but is hidden/undocumented, in which case the fix is in kosli-dev/cli (cmd/kosli/evaluatePolicy.go) and this entry should not link to a page that will never exist.
I could not fetch the upstream release notes from this job to settle which, so please confirm against kosli-dev/cli v2.43.0 before merging.
| ## Updates | ||
|
|
||
| - **Attestation commands survive missing repositories** — `kosli attest` commands now warn (instead of failing) when a CI-defaulted `--commit` cannot be resolved because no repository is checked out, letting jobs without a repo continue. | ||
| - **Clearer errors when commit info is required** — `kosli attest pullrequest-*` and [`kosli attest jira`](/client_reference/kosli_attest_jira) now emit a descriptive error when the commit cannot be resolved, instead of silently proceeding or panicking. Explicit `--commit` or `--repo-root` values that fail to resolve now name the fix. |
There was a problem hiding this comment.
Contradicts the generated reference — and the bullet above it.
The reference was generated from v2.43.1 (client_reference/overview.md:7), so it already contains this change. It documents the opposite behavior for kosli attest jira:
client_reference/kosli_attest_jira.md:98— "If both--commitand--repo-rootare left at their defaults and the commit cannot be read from the repository, a warning is printed and the attestation is sent without commit info."
Same text on client_reference/kosli_attest_pullrequest_azure.md:37. That is exactly what bullet 1 (line 11) describes, so as written the two bullets in this entry disagree about what kosli attest jira does when a defaulted commit can't be resolved.
The second sentence ("explicit --commit or --repo-root values that fail to resolve") is consistent with both — scoping the whole bullet to the explicit case would resolve the conflict.
Separately: pullrequest-* implies commands named pullrequest-github. The actual commands use a space — kosli attest pullrequest github|gitlab|azure|bitbucket (client_reference/kosli_attest_pullrequest_github.md:9).
This branch was successfully deployed
1 participant
Summary
Add changelog entries for four new CLI releases published in the scope window (Sep 14–21, 2026).
Changes
kosli evaluate policy(evaluate + record in one call).--sonar-revisionwith--pull-request; safer S3 key handling; drop legacyVisibilityfield; fixlist flowspanic.kosli attest sbom(beta); Sonar token no longer follows redirects; Azure snapshot zip and log-digest hardening; CycloneDX SBOM tool read fromservices.No new tags for
terraform-provider-kosli(last v0.9.4 is already logged) orserver(no tags) in the window.