docs: cli v2.36.4 and Aug 4-7 Platform releases - #357
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Claude finished @mintlify[bot]'s task in 1m 56s —— View job PR Review: Changelog updates
FindingsNo critical issues found. The entries are well-written, follow existing changelog conventions, and comply with CLAUDE.md. Improvement
Suggestions
What looks good
Build statusThe Mintlify preview deployment failed. This doesn't appear to be caused by the changelog content (format matches existing entries exactly). Worth checking the Mintlify dashboard for build logs. SummaryClean changelog PR with 4 well-structured entries. One minor link-text accuracy suggestion (inline comment posted) and one categorization suggestion. No blockers. |
|
|
||
| ## Bug fixes | ||
|
|
||
| - **`kosli attest` no longer fails on container-produced attachments** — passing two or more `--attachments` paths could abort with `chown ...: operation not permitted` when an attachment (for example lint, test, or coverage output) had been written by a Docker container running as a different user. The CLI no longer tries to preserve file ownership when staging attachments for upload. A genuine copy error now also names the evidence path you passed rather than an internal temp directory. See the [`kosli attest` reference](/client_reference/kosli_attest_artifact) for usage. |
There was a problem hiding this comment.
Suggestion: The link text says `kosli attest` reference but points to the kosli_attest_artifact page. Consider updating the text to match the actual target:
| - **`kosli attest` no longer fails on container-produced attachments** — passing two or more `--attachments` paths could abort with `chown ...: operation not permitted` when an attachment (for example lint, test, or coverage output) had been written by a Docker container running as a different user. The CLI no longer tries to preserve file ownership when staging attachments for upload. A genuine copy error now also names the evidence path you passed rather than an internal temp directory. See the [`kosli attest` reference](/client_reference/kosli_attest_artifact) for usage. | |
| - **`kosli attest` no longer fails on container-produced attachments** — passing two or more `--attachments` paths could abort with `chown ...: operation not permitted` when an attachment (for example lint, test, or coverage output) had been written by a Docker container running as a different user. The CLI no longer tries to preserve file ownership when staging attachments for upload. A genuine copy error now also names the evidence path you passed rather than an internal temp directory. See the [`kosli attest artifact` reference](/client_reference/kosli_attest_artifact) for usage. |
|
|
||
| ## Updates | ||
|
|
||
| - **SCIM role changes sync from Descope** — SCIM webhooks that carry a role or group change without a status field are no longer ignored. A user's Kosli membership is reconciled from Descope on every `SCIMUserModified` event, so a role change (for example member → admin) or the removal of a role now applies immediately. |
There was a problem hiding this comment.
This seems to be only internal changes. And SCIM is not referenced other places in the docs
|
|
||
| ## Updates | ||
|
|
||
| - **Richer override attestation view** — override attestations now render a dedicated summary showing the reason, the original attestation's type and status, and a link to the overridden attestation, instead of the raw JSON payload. |
There was a problem hiding this comment.
What is the "override attestation view"? and is it something we want to have in the changelog?
Summary
Adds changelog entries for CLI v2.36.4 and the Platform releases dated August 4, 5, and 7, 2026.
Changes
kosli attestattachments fix (no longer chowns when staging multi-path attachments).flow_tag./api/*returns JSON 404.Context
kosli-dev/terraform-provider-koslitags in window.