| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Sorry, something went wrong.
|
Claude finished @mbevc1's task in 1m 54s —— View job Doc review — PR #371
No Critical findings. Two Suggestions, both posted inline. Nothing blocks merge. changelog/index.mdxWhat's verified good
Suggestions (inline)
Note on the PR title — chore: fix ordering and a typo undersells the first hunk. It documents a previously-undocumented --summary flag, adds the mutual-exclusivity constraint, and adds a reference link. docs: or fix: would describe it more honestly; both are valid Conventional Commits types per CLAUDE.md. Not run: mint broken-links — the CLI isn't installed in this runner. I verified each changed link's target by file path and navigation entry instead, which covers the links this PR touches but not the rest of the site. |
Sorry, something went wrong.
| ## New features | ||
|
|
||
| - **Custom attestation type summaries** — `kosli create attestation-type` and `kosli update attestation-type` now accept `--summary-json`, a JSON list of ordered `{name, expression}` entries. Each expression is a jq expression evaluated against the attestation payload, and Kosli renders the results as labeled rows on the attestation detail page. See [custom attestation types](/getting_started/attestations). | ||
| - **Custom attestation type summaries** — `kosli create attestation-type` now accepts `--summary`, a repeatable `'NAME=EXPRESSION'` entry (for example `--summary "Critical=.critical_count"`), and `--summary-json`, the same list given as a JSON array of `{name, expression}` entries. Each expression is a jq expression evaluated against the attestation payload, and Kosli renders the results as labeled rows on the attestation detail page, in the order given. The two flags cannot be combined. See [custom attestation types](/getting_started/attestations) and the [`kosli create attestation-type` reference](/client_reference/kosli_create_attestation-type). |
There was a problem hiding this comment.
Suggestion — the rewrite is accurate: it matches client_reference/kosli_create_attestation-type.md:28-50 (repeatable --summary, JSON --summary-json, "The two summary flags cannot be combined"), and dropping kosli update attestation-type is a real correctness fix — that command doesn't exist, kosli create attestation-type is documented as "Create or update".
One loose end: the first link, /getting_started/attestations, doesn't mention summaries anywhere on the page (no summary match in getting_started/attestations.md). A reader following it for summary docs lands on nothing. Either add a short summaries section to that page or drop the link and keep only the reference link, which does cover it.
Sorry, something went wrong.
|
|
||
| </Update> | ||
|
|
||
| <Update label="August 18, 2026" description="v2.37.0" tags={["CLI"]}> |
There was a problem hiding this comment.
Suggestion — the date ordering fix is correct; the whole file is now strictly descending by label.
Within August 18 the order is now Platform → CLI → Terraform. On every other shared date in this file the Platform entry comes last: Aug 19 (CLI, Platform), Aug 14 (CLI, Platform), Jul 31 (CLI, Platform), Jul 28 (CLI, CLI, Platform), Jul 10 (Terraform, CLI, Platform), Jul 8 (CLI, Terraform, Platform). Moving this v2.37.0 block above the Aug 18 Platform entry (currently line 40) would match that convention.
Non-blocking — it only affects same-day grouping, not the date ordering this PR set out to fix.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Minor fixes following #370