Repository navigation
Tags
Tags
# Breaking changes - `kosli attest in-toto --source github`: when no signer is pinned, the default signer now only accepts an attestation made by the run this command is part of (including earlier attempts of that run), instead of any workflow run matching the repository's identity pattern. This closes a gap where anyone able to push a branch or open a pull request could have their own attestation of the artifact accepted under the default signer. Attestations made by another run (e.g. a deployment workflow) now require pinning the signer explicitly with `--certificate-identity`/`--certificate-identity-regexp` and `--certificate-oidc-issuer`, or `--key`. - The `attestation` external URL recorded for attestations read from GitHub's listing (when there is no public transparency log entry) no longer carries a fingerprint, since that listing covers every attestation of the artifact rather than only the one recorded. # New features - `--repository` can now be given as `owner/name` directly with `--source github`, letting the owner be read from `--repository` alone instead of requiring `--github-org`. - Added validation that catches a `--github-org` which conflicts with the owner named in `--repository`, with clear error messages, including when the repository came from GitHub Actions defaults. - When an attestation cannot be recorded because it was made by another run, the error now names the flags that pin a signer to record it anyway. # Improvements - Updated the `--cloud-run-resolve-names` flag description to reference the correct required permission (`artifactregistry.dockerimages.get`).
# Breaking changes - `list product-updates` now lists only unread updates by default, capped at the first 10; use `--all` to also list updates you've already seen, and `--limit` to change or remove the cap (`--limit 0` for no limit). # New features - `attest in-toto` gains `--source github` to read the attestations GitHub holds for an artifact (as stored by `actions/attest`), with new `--github-org` and `--repository` flags; it is the default source when running inside GitHub Actions. - `list product-updates` gains `--dismiss` to mark the unread updates listed as seen. - `list audit-logs` gains new aliases `al` and `als`.
# New features - Added `kosli attest in-toto` command (beta) to record in-toto attestations (e.g. SLSA provenance or SBOM) that a build already produced, verifying the attestation's signature via Sigstore before recording it. - Added experimental (beta) support for running a build command as part of `kosli attest artifact` via `-- BUILD-COMMAND...`; the artifact is fingerprinted and attested only if the build succeeds, with new `--record-build-command` flag and `build_command`/`build_duration_seconds` annotations recorded automatically.
# Bug fixes - `evaluate` commands now consistently print an empty `violations` list as `[]` instead of `null`, matching output between local and server-side evaluation paths.
# Bug fixes - Fixed incorrect GitHub references in the `kosli assert mergerequest gitlab` and `kosli attest pullrequest gitlab` command examples, which now correctly show GitLab flag names and values. # Improvements - Clarified the `--gitlab-token` flag description to note it needs the `read_api` scope.
# Bug fixes - Honour the `Retry-After` value sent by the server on a 409 conflict (lock contention) response, capped at one minute, instead of using a fixed exponential backoff.
# Improvements - HTTP errors from the Kosli API, policy fetches, and Bitbucket PR evidence calls now report a clear status like `HTTP 409 Conflict` instead of a bare code or a confusing JSON-parse error. - Non-JSON error responses (e.g. proxy/CDN pages) now report their HTTP status, with the raw body available via `--debug`. - Retry backoff is now jittered to avoid clients retrying in lockstep after shared failures.
# Bug fixes - Fixed shared global timeago configuration being mutated across calls, which could cause incorrect "ago" suffixes in `list snapshots` and `get snapshot` output. - Fixed home directory resolution (used for default config file and kubeconfig lookup) to prefer the `HOME` environment variable, improving compatibility with Cygwin/MSYS2 shells on Windows.
# New features - `kosli snapshot azure` now supports `--include`, `--include-regex`, `--exclude` and `--exclude-regex` flags to filter which Azure web/function apps are snapshotted by name or regex pattern. - `kosli snapshot azure` now supports `--azure-cloud`, `--azure-authority-host` and `--azure-resource-manager-url` flags to snapshot apps running in Azure China, Azure Government, or private/custom Azure clouds. # Improvements - `kosli snapshot cloud-run` now validates include/exclude filter flags (including regex patterns) upfront before making any GCP calls, and warns when the filters leave out every service and job. - `kosli snapshot ecs`, `kosli snapshot k8s` and `kosli snapshot lambda` now validate include/exclude regex filters earlier and consistently, with clearer error messages for invalid regex patterns.
PreviousNext