> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cysmiq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud updates

> New features, improvements, and bug fixes available in Cysmiq Cloud.

<Update label="August 19, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Bitbucket repositories now follow default branch changes more reliably.
</Update>

<Update label="August 18, 2026" tags={["New features"]}>
  ## New features

  * The Cysmiq sidebar now shows current service status and links to the [public status page](https://status.cysmiq.com/).
</Update>

<Update label="August 15, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Fixed scan result processing for repositories with deeply nested file paths so Cysmiq processes findings, manifests, and pull request comparisons reliably.
</Update>

<Update label="August 14, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Re-enabled repositories now resume scanning more reliably when earlier scans are still active.
  * Bitbucket Cloud connections can now be saved even when Bitbucket temporarily limits an optional setup request.
</Update>

<Update label="August 13, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Dependency policy violations, counts, and filters now stay accurate after incremental scans.
</Update>

<Update label="August 12, 2026" tags={["Improvements", "Bug fixes"]}>
  ## Improvements

  * Queued scans now make progress more consistently across repositories when scan capacity is limited.

  ## Bug fixes

  * Improved scan stability when analysis tasks time out by cleaning up unfinished processing more reliably.
  * Fixed vulnerability detail pages so location counts resolve correctly and the **Activity** tab preserves accurate status, resolution, snooze, and transition-comment history.
</Update>

<Update label="August 11, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Fixed pull request assessments that reuse older scan results with skipped paths so complete evaluations no longer remain pending.
</Update>

<Update label="August 10, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Fixed code vulnerability analysis so newer local results take precedence over stale or late call-chain evidence.
  * Fixed pagination on the **Users** and **Invitations** tabs so workspaces with more than 20 entries can browse every member and invitation.
  * Fixed scan recovery when source history is unavailable so affected repositories can continue from the current repository state instead of remaining blocked.
  * Scanning remains unavailable for archived repositories until Cysmiq confirms they are active.
</Update>

<Update label="August 9, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Fixed GitHub push and pull request event processing during maintenance or transient failures so affected scans and assessments can resume.
</Update>

<Update label="August 6, 2026" tags={["New features", "Improvements", "Bug fixes"]}>
  ## New features

  * The [Cysmiq API](/api-reference/introduction) now identifies whether a vulnerability comes from the current branch state or Git history and can filter vulnerability lists by that source.

  ## Improvements

  * [Vulnerability detail pages](/vulnerability-management/vulnerability-detail-view#scan-scoped-evidence) now provide a dedicated **Locations** tab and preserve the originating scan's branch or tag when opened from a scan-filtered vulnerability list.

  ## Bug fixes

  * GitHub status checks no longer include internal scan or policy diagnostics in their public output.
  * Fixed pull request assessments for changes that include paths excluded from scanning so complete evaluations no longer remain pending because of those paths.
  * Fixed stale table counts that could appear after navigating quickly between large views.
</Update>

<Update label="August 5, 2026" tags={["New features", "Improvements", "Bug fixes"]}>
  ## New features

  * The [Scans view](/scanning/scan-list-view#live-scan-progress) now shows live analysis phases, progress through the scan pipeline, item counts, and estimated time remaining when enough comparable scan history is available.

  ## Improvements

  * Pull request assessment and policy status checks now show clearer outcome summaries across connected version control providers. GitHub checks also include contributing pull request results and links to relevant Cysmiq results.
  * Filters load faster in large vulnerability, policy violation, and package views.

  ## Bug fixes

  * Metadata-only pull request and merge request edits no longer start redundant assessments when the compared commits are unchanged.
  * Fixed GitHub pull request assessments when changed-file counts differ between GitHub API responses.
  * Fixed source preparation for repositories with branch or tag names that contain Unicode whitespace.
  * Various bug fixes improved scan recovery and result processing for large or long-running scans.
</Update>

<Update label="August 4, 2026" tags={["Improvements"]}>
  ## Improvements

  * Improved source preparation reliability for concurrent scans, including cache reuse and safer recovery under storage pressure.
</Update>

<Update label="August 2, 2026" tags={["Improvements", "Bug fixes"]}>
  ## Improvements

  * Incremental scans can now reuse completed analysis from scans that later failed during an unrelated step, reducing unnecessary full scans.

  ## Bug fixes

  * Fixed layout and wrapping in repository branch and tag tables.
</Update>

<Update label="August 1, 2026" tags={["Improvements", "Bug fixes"]}>
  ## Improvements

  * Secret scan controls and progress details now use **Provider checks** and **Context assessments**, making the two assessment methods easier to distinguish. See [Repository scan jobs](/assets/repositories#scan-jobs).
  * Large asset, vulnerability, scan, and policy tables now load faster.
  * Improved finding ingestion performance for scans that produce large result sets.

  ## Bug fixes

  * Various bug fixes improved scan completion and recovery when tasks are delayed or run concurrently.
</Update>

<Update label="July 28, 2026" tags={["New features", "Bug fixes"]}>
  ## New features

  * The [Repositories](/assets/repositories#repository-list) and [Scans](/scanning/scan-list-view#filters) views now show available repositories by default and provide an **Availability** filter for switching to orphaned repositories or all repositories.

  ## Bug fixes

  * Fixed scan post-processing for large vulnerability candidate sets so affected scans can complete successfully.
  * Fixed Secret History scanning so only repository content produces findings and missing commit details no longer interrupt result processing.
</Update>

<Update label="July 26, 2026" tags={["New features", "Bug fixes"]}>
  ## New features

  * [Repository scan-job settings](/assets/repositories#scan-jobs) now let teams choose which analyses run and limit call-chain analysis to selected branches. Code analysis, call chains, and Secret History are automatically skipped for monorepos.

  ## Bug fixes

  * Various bug fixes improved scan orchestration, pull request assessment recovery, and dependency policy evaluation.
</Update>

<Update label="July 25, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Fixed SBOM result processing for dependencies with unusually long package identifiers so affected scans can complete.
</Update>

<Update label="July 24, 2026" tags={["Improvements", "Bug fixes"]}>
  ## Improvements

  * The [vulnerability Analysis view](/vulnerability-management/vulnerability-detail-view) can now filter call hierarchies by path, branch or ref, and analysis state, making large result sets easier to review.

  ## Bug fixes

  * Improved scan and pull request assessment reliability during concurrent processing.
</Update>

<Update label="July 22, 2026" tags={["Improvements", "Bug fixes"]}>
  ## Improvements

  * The [Scans view](/scanning/scan-list-view) now shows repositories and organizations separately, links repository names to their Cysmiq detail pages, and keeps full names and identity details available on hover.

  ## Bug fixes

  * Dependency policy results now remain scoped to the correct repository when applications or environments span multiple repositories. Removed dependency evidence and policy exceptions now update matching violations consistently.
  * Various bug fixes improved scan completion, SBOM result processing, and Bitbucket pull request assessments.
</Update>

<Update label="July 21, 2026" tags={["New features", "Improvements", "Bug fixes"]}>
  ## New features

  * [VCS status and PR decoration settings](/scanning/vcs-status-updates) can now set the minimum finding severity that blocks security checks and choose which terminal pull request results receive comments.

  ## Improvements

  * Pull request comments now separate blocking findings, non-blocking warnings, exploitability changes, fixed findings, and policy outcomes, with links to the relevant Cysmiq results.

  ## Bug fixes

  * Bitbucket Cloud integration setup now identifies Atlassian account API tokens and app passwords and directs users to the required workspace access token.
  * Fixed the vulnerability status dialog so its displayed resolution is selected correctly.
  * Workspace listings no longer include workspaces scheduled for deletion.
  * Improved pull request assessment reliability for large result sets.
</Update>

<Update label="July 20, 2026" tags={["Improvements"]}>
  ## Improvements

  * Improved scan monitoring and pull request assessment performance.
</Update>

<Update label="July 19, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Fixed analysis result processing so scans only update findings for the repository being analyzed.
  * Fixed GitHub pull request comment recovery when an existing comment can no longer be found.
  * Various bug fixes improved scan recovery and pull request assessment consistency.
</Update>

<Update label="July 17, 2026" tags={["New features", "Bug fixes"]}>
  ## New features

  * [Repository branch views](/assets/repositories#branch-scan-actions) can now start scans for unscanned branches and retry eligible failed scans. Failed scans can also be retried from the [Scans view](/scanning/scan-list-view#drill-down-actions).

  ## Bug fixes

  * Various bug fixes improved scan queue reliability and pull request assessment consistency.
</Update>

<Update label="July 16, 2026" tags={["New features"]}>
  ## New features

  * [Code scanning](/scanning/code) now supports Swift and Dart. Framework-aware coverage includes CryptoSwift and SwiftNIO for Swift, plus common database and WebView packages for Dart.
  * [Dependency scanning](/scanning/dependencies) now recognizes Dart Pub projects and CocoaPods dependencies in Swift projects.
</Update>

<Update label="July 15, 2026" tags={["Improvements", "Bug fixes"]}>
  ## Improvements

  * Secret findings now identify whether Cysmiq used a provider check or a context assessment. Dedicated filters and badges make the assessment method easier to understand during triage. See [Secrets scanning](/scanning/secrets#assessment-methods).

  ## Bug fixes

  * Fixed analysis of Scala Play configuration findings so affected scans can complete successfully.
  * Various bug fixes improved GitHub and Bitbucket Cloud integration reliability.
</Update>

<Update label="July 14, 2026" tags={["New features"]}>
  ## New features

  * [Code scanning](/scanning/code) now supports Rust, including framework-aware rules for libraries such as Diesel, Reqwest, SQLx, Tower HTTP, and Warp.
  * Code scanning now supports Scala, including framework-aware rules for Akka HTTP, Anorm, Play, and Slick.
  * [Dependency scanning](/scanning/dependencies) now recognizes Scala projects that use sbt manifests and lock files.
</Update>

<Update label="July 13, 2026" tags={["Bug fixes"]}>
  ## Bug fixes

  * Various bug fixes improved pull request assessment consistency and pull request decoration behavior.
</Update>

<Update label="July 8, 2026" tags={["New features", "Improvements", "Bug fixes"]}>
  ## New features

  * [Code scanning](/scanning/code) now supports Ruby, including Rails-aware analysis, ERB templates, and common Ruby project files.
  * Code scanning now supports Kotlin, including framework-aware coverage for Android projects and Apache HTTP Client usage.

  ## Improvements

  * Improved reliability for large code scans by reducing memory use during call-chain analysis.

  ## Bug fixes

  * Improved scan completion and recovery when result processing times out.
  * Prevented cancelled scans from being queued again during recovery.
</Update>

<Update label="July 2, 2026" tags={["New features", "Action required"]}>
  ## New features

  * [Code scanning](/scanning/code) now supports Elixir, including framework-aware rules for Phoenix and Plug applications.
  * The [Cysmiq CLI](/reference/cli#list-tenants-repositories-and-applications) can now list accessible workspaces, repositories, and applications, making it easier for scripts and coding agents to discover the identifiers they need.
  * CLI checks, vulnerability lists, and vulnerability summaries can now target an application across its repositories.

  ## Action required

  * Existing API keys retain their original scopes. Create a key with `tenants:read` or `applications:read` when using the new tenant and application commands. See [API keys](/security-access/api-keys).
</Update>

<Update label="June 30, 2026" tags={["New features", "Bug fixes"]}>
  ## New features

  * The [Cysmiq CLI](/reference/cli#agent-skills) can now install, inspect, update, and remove official Cysmiq skills for Codex, Claude Code, and portable agent layouts.

  ## Bug fixes

  * Disabled repositories no longer publish new VCS status updates until scanning is re-enabled. See [VCS status updates](/scanning/vcs-status-updates#what-disabling-affects).
</Update>

<Update label="June 25, 2026" tags={["New features", "Improvements"]}>
  ## New features

  * Pull requests can now show separate **Cysmiq Scan**, **Cysmiq PR Assessment**, and **Cysmiq Policies** checks, making scan execution, vulnerability assessment, and policy enforcement independently visible. See [VCS status checks](/scanning/vcs-status-updates#vcs-status-checks).

  ## Improvements

  * The [Scans view](/scanning/scan-list-view#status-and-result-labels) now separates lifecycle **Status** from the resulting pull request or provider outcome, including scans associated with multiple current pull requests.
</Update>