-
Notifications
You must be signed in to change notification settings - Fork 1
docs: add changelog entries for CLI v2.27.0, v2.28.0, and platform updates #282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mintlify
wants to merge
1
commit into
main
Choose a base branch
from
mintlify/84c84371
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+58
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -4,6 +4,64 @@ description: "Release notes for Kosli products." | |||||
| rss: true | ||||||
| --- | ||||||
|
|
||||||
| <Update label="June 22, 2026" description="" tags={["Platform"]}> | ||||||
|
|
||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggestion: "V2" uses an uppercase V, while CLI versions elsewhere use lowercase (
Suggested change
|
||||||
| ## New features | ||||||
|
|
||||||
| - **Membership audit log page** — the membership/role-change history now has a dedicated **Audit Log** page under Settings → User Management, with search, filters (event type, role, source), date range, and sortable columns. | ||||||
| - **Stronger code-review control (SDLC-CTRL-0007)** — now requires every commit in the merged PR to be signed (`verified == true`) and the PR to merge into the protected branch, building on the new `verified`, `signature_state`, and `base_ref` fields in `pull_request` attestations. | ||||||
| - **`pull_request` attestation fields** — V2 `pull_request` attestations now carry per-commit `verified` / `signature_state` and a PR `base_ref` (populated by CLI v2.27.0+), enabling Rego policies for signed commits and "merged into main". | ||||||
| - **Service account CRUD API** — new JSON endpoints under `/service-accounts/{org}` to create, list, get, update, and delete service accounts, complementing the existing API-key endpoints. | ||||||
|
|
||||||
| ## Updates | ||||||
|
|
||||||
| - **Artifact name on control decisions** — the decisions list and decision tray now show a human-readable artifact name alongside the fingerprint. | ||||||
| - **Decision list columns** — added **control version** and **attestation name** columns to the decisions list. | ||||||
| - **Auto-run deletability check** — initiating an org-deletion plan now runs the deletability check automatically, with an approval-blocker warning banner on each plan card when checks fail; the manual button is renamed **Re-check deletability**. | ||||||
| - **Archived date for shared orgs** — the Archived tab on `/organizations/shared` now shows an **Archived on** column. | ||||||
| - **Controls UI refresh** — the controls list, control detail, control edit/new form, and version list pages have been restyled with new layouts, filtering, and interaction improvements. | ||||||
| - **Faster environment snapshot listing** — `GET /api/v2/snapshots/{org}/{env_name}` (and `kosli list snapshots`) is significantly faster on large/long-lived environments by eliminating per-snapshot ordinal seeks and discarded counts. | ||||||
| - **Display name fallback** — audit log, controls, and trail views now fall back to `login_name` when a user has no display name set. | ||||||
| - **Signup form** — the welcome signup form now shows field labels. | ||||||
| - **Wording** — "Logout" is now "Sign out" across the app. | ||||||
| - **`base_ref` field placement** — in serialized `pull_request` attestation JSON, `base_ref` now sits next to `head_ref` (cosmetic; key order is not significant). | ||||||
|
|
||||||
| ## Bug fixes | ||||||
|
|
||||||
| - **Concurrent create 500s** — fixed 500 errors on concurrent `PUT /api/v2/trails/{org}/{flow}` (begin trail) and `PUT /api/v2/policies/{org}/{name}` requests by retrying on duplicate-key races. | ||||||
| - **"Added" date reset on role change** — fixed a regression where changing a user's role reset their **Added** date (and the service account **Created** date) to today; both now read the original `created_at`. | ||||||
|
|
||||||
| </Update> | ||||||
|
|
||||||
| <Update label="June 18, 2026" description="v2.28.0" tags={["CLI"]}> | ||||||
|
|
||||||
| ## New features | ||||||
|
|
||||||
| - **`kosli get trail --output markdown`** — `get trail` now supports GitHub-Flavored Markdown output, suitable for piping into CI job summaries (e.g. `$GITHUB_STEP_SUMMARY`). The output includes trail metadata, git commit info, attestation statuses with compliance indicators and links to the Kosli app, and an events table with linked commit SHAs, environment snapshots, and attestation references. See the [get trail reference](/client_reference/kosli_get_trail). | ||||||
|
|
||||||
| [View on GitHub](https://github.com/kosli-dev/cli/releases/tag/v2.28.0) | ||||||
|
|
||||||
| </Update> | ||||||
|
|
||||||
| <Update label="June 16, 2026" description="v2.27.0" tags={["CLI"]}> | ||||||
|
|
||||||
| ## New features | ||||||
|
|
||||||
| - **`pull_request` attestations capture commit signatures and PR base branch** — each commit now records `verified` and `signature_state` (GitHub and GitLab), and every PR records `base_ref` (GitHub, GitLab, Bitbucket, Azure DevOps), enabling Rego policies for signed commits and "merged into main". Bitbucket and Azure DevOps don't expose per-commit signature verification, so those fields are omitted for them. | ||||||
|
|
||||||
| ## Updates | ||||||
|
|
||||||
| - **`pull_request` attestation commits** — record the git **author** identity and authored timestamp (not the committer) across all providers. | ||||||
| - **API key rotation** — failures now clean up the duplicate key ID and include details in the error response. | ||||||
|
|
||||||
| <Warning> | ||||||
| The new `base_ref` field is rejected by Kosli servers older than the matching server change. **Self-hosted users must upgrade their Kosli server before upgrading this CLI**, otherwise `pull_request` attestations will fail validation. Kosli SaaS (app.kosli.com / app.us.kosli.com) is already updated. | ||||||
| </Warning> | ||||||
|
|
||||||
| [View on GitHub](https://github.com/kosli-dev/cli/releases/tag/v2.27.0) | ||||||
|
|
||||||
| </Update> | ||||||
|
|
||||||
| <Update label="June 12, 2026" description="" tags={["Platform"]}> | ||||||
|
|
||||||
| ## New features | ||||||
|
|
||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion (minor): "the PR to merge into the protected branch" reads slightly ambiguously. Consider "the PR to target the protected branch" or "the PR to be merged into the protected branch".