<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title><![CDATA[Changelog]]></title>
        <description><![CDATA[New features, improvements, and fixes across Qlty Cloud and the Qlty CLI]]></description>
        <link>https://docs.qlty.sh</link>
        <generator>Mintlify</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:45:21 GMT</lastBuildDate>
        <atom:link href="https://docs.qlty.sh/changelog/rss.xml" rel="self" type="application/rss+xml"/>
        <copyright><![CDATA[Qlty Docs]]></copyright>
        <docs>https://docs.qlty.sh</docs>
        <item>
            <title><![CDATA[Java plugins move to Java 25 after the eMudhra CA compromise]]></title>
            <description><![CDATA[The Qlty CLI now runs Java-based plugins on Temurin 25, which rejects certificates from the compromised eMudhra certificate authorities. radarlint-kotlin moves to 2.1.0, which reports more Kotlin issues.]]></description>
            <link>https://docs.qlty.sh/changelog#october-29-2026</link>
            <guid isPermaLink="false">9831c331b88c8439</guid>
            <category><![CDATA[CLI]]></category>
            <category><![CDATA[Cloud]]></category>
            <category><![CDATA[Plugins]]></category>
            <pubDate>Thu, 29 Oct 2026 18:21:16 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Java plugins run on Java 25</h2>
<p>Java-based plugins such as Checkstyle, PMD and radarlint can fetch configs or rulesets over HTTPS while they run. The CLI's previous default Java, Temurin 22.0.1+8, still trusts the compromised eMudhra certificate authorities, so it would accept a forged certificate.</p>
<p>Starting with CLI v0.664.0, the default Java runtime is Temurin 25.0.5+8, which rejects those certificates. Qlty Cloud picks up the new CLI automatically. See the <a href="https://github.com/qltysh/qlty/security/advisories/GHSA-f55x-97q4-pfrc">security advisory</a> for details.</p>
<p>If you followed the advisory and added <code>java = "25.0.5+8"</code> under <code>[runtimes.enabled]</code>, you can remove it. Any other Java version you pin stays in effect. See <a href="https://docs.qlty.sh/cli/concepts/runtimes">Runtimes</a>.</p>
<h2>radarlint-kotlin 2.1.0 reports more Kotlin issues</h2>
<p>radarlint-kotlin moves to 2.1.0. It bundles a newer SonarSource Kotlin analyzer that runs on Java 25. The new analyzer resolves the types in your code, so existing rules find issues the old one missed. It also parses newer Kotlin syntax, such as guards in <code>when</code> branches, so files the old one skipped now get analyzed.</p>
<p>Expect more Kotlin issues on your default branch. In our tests on open source projects, the count rose by 4% to 15%. Pull requests flag only the issues on lines they add, so code a PR doesn't touch adds nothing to it.</p>
<p>Three rules report false positives with the new analyzer:</p>
<ul>
<li><strong><code>kotlin:S1128</code> (unused imports)</strong> flags imports used only in annotations or KDoc, and imports that share a name with a local declaration. SonarSource's later Kotlin analyzers no longer report this rule.</li>
<li><strong><code>kotlin:S1862</code> (same condition in related branches)</strong> ignores <code>when</code> guards, so it flags branches that differ only in their guard.</li>
<li><strong><code>kotlin:S6619</code> (useless null checks)</strong> flags some null checks on map lookups that can return null.</li>
</ul>
<p>To turn a rule off, add a line to <code>radarlint.properties</code> in your project root:</p>
<p>See <a href="https://docs.qlty.sh/cli/radarlint-configuration">Radarlint Configuration</a>.</p>
<h2>Pinned plugin versions that fail on Java 25</h2>
<ul>
<li><strong>radarlint-kotlin 2.0.0 and earlier</strong> analyze nothing on Java 25 and report no error. Upgrade to 2.1.0.</li>
<li><strong>google-java-format 1.26.0 and earlier</strong> crash on Java 25. Upgrade to 1.27.0 or later.</li>
</ul>
<p>If you can't upgrade yet, pin <code>java = "22.0.1+8"</code> under <code>[runtimes.enabled]</code>. Java 22 still trusts the compromised certificate authorities, so remove the pin as soon as you upgrade.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automatic coverage setup: one click and a pull request]]></title>
            <description><![CDATA[Setting up coverage reporting usually means pushing CI changes and waiting on the test suite until the upload works. Now Qlty Cloud's agent reads your CI and opens a draft pull request with the change, and you review and merge it.]]></description>
            <link>https://docs.qlty.sh/changelog#october-13-2026</link>
            <guid isPermaLink="false">678f6b70f03b25c6</guid>
            <category><![CDATA[Cloud]]></category>
            <category><![CDATA[Coverage]]></category>
            <pubDate>Tue, 13 Oct 2026 14:22:30 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Automatic coverage setup</h2>
<p>Setting up coverage reporting on CI usually goes in a loop. You add the upload step, push, and wait for the test suite. A flag or a path is wrong, so you fix it, push, and wait again. Automatic coverage setup hands that work to Qlty Cloud's agent.</p>
<p>Open <strong>Project Settings → Code Coverage</strong>, click <strong>Set up coverage</strong>, and on the <strong>Automatic</strong> tab click <strong>Set up automatically</strong>. A few minutes later there's a draft PR titled <strong>Set up Qlty code coverage</strong> on your repository, with the agent's report as its description. Review it and merge it, and the next CI run on your default branch sends coverage.</p>
<p>The agent runs in an isolated build container with a copy of your default branch. It reads your CI configuration and test setup, and writes the smallest change that produces complete coverage. On GitHub Actions it uses OIDC, so there's no secret to add. It can't commit, push, add secrets or merge. Qlty turns its edits into the PR.</p>
<p>We've tested it on GitHub Actions. On CircleCI and other providers, review the PR with extra care. If the PR's CI fails, the same page lets you run Qlty's open source <a href="https://github.com/qltysh/qlty-skills/tree/main/skills/setup-coverage"><code>setup-coverage</code> skill</a> in your own coding agent, or set coverage up by hand.</p>
<p>Starting a run needs the <strong>admin</strong> role on the project, and the <a href="https://docs.qlty.sh/cloud/github-app">Qlty GitHub App</a> needs the <strong>Workflows</strong> permission. If it's missing, the setup page links to where an organization owner can <a href="https://docs.qlty.sh/cloud/github-app#accepting-new-permissions">accept it</a>. To set up coverage, Qlty sends your repository's default branch to an AI subprocessor, currently Anthropic, which does not train models on it. See <a href="https://docs.qlty.sh/cloud/data-usage">Data Usage</a>.</p>
<p>See <a href="https://docs.qlty.sh/coverage/automatic-setup">Automatic Coverage Setup</a> for details.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is the code your team is shipping well covered?]]></title>
            <description><![CDATA[Total coverage is a lagging metric on a large Project, while diff coverage is a leading one. Every Project's Trends page now charts diff coverage week by week.]]></description>
            <link>https://docs.qlty.sh/changelog#august-31-2026</link>
            <guid isPermaLink="false">2874d744cd62a9cd</guid>
            <category><![CDATA[Cloud]]></category>
            <category><![CDATA[Coverage]]></category>
            <pubDate>Mon, 31 Aug 2026 03:08:59 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Is the code your team is shipping well covered?</h2>
<p>Most coverage trend charts plot a Project's total coverage over time. That's valuable, but on a large project total coverage is a lagging metric: a real change in how a team tests takes a long time to make a meaningful mark on the total. Diff coverage — the coverage of the lines a change touches — is a leading one. If your team is covering the code it ships, diff coverage is high now, and total coverage trends upward over time.</p>
<p>Every Project's <strong>Trends</strong> page now includes a <strong>Diff Coverage</strong> chart, showing how well tested the code you merged was, week by week. Diff coverage is plotted as a line, with the executable lines changed in each period as bars behind it, so you can tell a meaningful week from a quiet one. Ranges run from 1 month to 3 years.</p>
<p>There's nothing to configure — the chart is built from the coverage you already upload on your default branch. See <a href="https://docs.qlty.sh/coverage/diff-coverage-trends">Diff Coverage Over Time</a> for details.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Give your linters a token without committing it]]></title>
            <description><![CDATA[Build Secrets are encrypted, per-project environment variables for your cloud builds. Add one under Project Settings, and Qlty passes it only to the plugins that name it.]]></description>
            <link>https://docs.qlty.sh/changelog#august-5-2026</link>
            <guid isPermaLink="false">5443ccc847c824ec</guid>
            <category><![CDATA[Cloud]]></category>
            <category><![CDATA[Plugins]]></category>
            <pubDate>Mon, 31 Aug 2026 04:18:14 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Build Secrets (beta)</h2>
<p>Some linters need a credential to do their job: an API token to reach a private package registry, a license key for a commercial tool. Until now, there was no way to hand one to a cloud build without committing it to your repository.</p>
<p><strong>Build Secrets</strong> are encrypted environment variables you set per project. Open <strong>Project Settings → Secrets</strong>, add a name and a value, and it's available to that project's builds. Values are write-only — once saved, a secret is encrypted and can never be read back, only rotated or deleted. The list shows names and timestamps, and only project admins can see or change it.</p>
<p>Adding a secret doesn't hand it to every plugin. The Qlty CLI runs each plugin in a subprocess with a restricted environment and passes through only the variables that plugin's definition names, so you opt each plugin in from your <code>qlty.toml</code>:</p>
<p>Secrets reach your plugins only while Qlty installs and runs them, and never reach builds for pull requests from forks.</p>
<p>Build Secrets are in beta and rolled out per workspace — <a href="https://qlty.sh/contact/support">contact Qlty Support</a> to request access. See <a href="https://docs.qlty.sh/cloud/build-secrets">Build Secrets</a> for details.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coverage for pull requests that run only the tests they need]]></title>
            <description><![CDATA[Test optimization tools run a different subset of tests every build, so the coverage they report has never been usable. Selective Coverage, now in beta, overlays that report on the pull request's diff.]]></description>
            <link>https://docs.qlty.sh/changelog#july-23-2026</link>
            <guid isPermaLink="false">7dc1348fed8205a3</guid>
            <category><![CDATA[CLI]]></category>
            <category><![CDATA[Cloud]]></category>
            <category><![CDATA[Coverage]]></category>
            <pubDate>Mon, 31 Aug 2026 05:55:53 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Selective Coverage on pull requests (beta)</h2>
<p>Qlty has always supported partial test runs through <a href="https://docs.qlty.sh/coverage/tags">tags</a>. Publish your unit tests as <code>units</code> and that suite is tracked on its own, because a tag runs a predictable set of tests each time and every report for it is comparable to the last.</p>
<p>Test optimization tools break that assumption. To keep pull request builds fast on a large codebase, they choose a different subset of tests for every build based on what the change touched. Each report covers a unique slice of the codebase, comparable to nothing before it, and to a coverage tool it looks like a sudden, dramatic drop. The coverage such a run reports would be misleading, so our recommendation has been not to publish it at all.</p>
<p><strong>Selective Coverage</strong> makes those runs usable by overlaying the selected report on the pull request's diff. Add <code>--selection</code> to <code>qlty coverage publish</code> in the builds that run a dynamically selected subset of your tests:</p>
<p>Qlty trusts a selected report for the lines it does cover — exactly what diff coverage needs — so the Diff Coverage commit status and PR comments work as usual. The Total Coverage status passes with "Not computable for select coverage" rather than a misleading percentage; total coverage metrics, component coverage, trends, and the file explorer are untouched; and a selected report is never used as the comparison base for another pull request.</p>
<p>Selective Coverage is in beta and requires Qlty CLI v0.633.0, GitHub Action <code>qltysh/qlty-action</code> v2.3.0, or CircleCI orb <code>qltysh/qlty-orb</code> 0.1.2 — or newer. Publish full-suite coverage on your default branch to keep totals and baselines accurate. See <a href="https://docs.qlty.sh/coverage/selective-coverage">Selective Coverage</a> for details.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[June 12, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#june-12-2026</link>
            <guid isPermaLink="false">97aa63e4feab6053</guid>
            <category><![CDATA[CLI]]></category>
            <category><![CDATA[Cloud]]></category>
            <category><![CDATA[Coverage]]></category>
            <category><![CDATA[Plugins]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Seat-based licensing</h2>
<p>Qlty Cloud now licenses Workspaces by <strong>seats</strong> instead of active contributors. A new <strong>Seat Management</strong> settings page lets admins assign seats to contributors and see how many are in use. See <a href="https://docs.qlty.sh/cloud/billing/seats">Seats</a> for details.</p>
<h2>Verified seat assignment</h2>
<p>When you assign a seat on the Seat Management page, Qlty now verifies the GitHub username exists before granting the seat. A confirmation dialog shows the account's avatar, name, and whether they belong to your GitHub organization, so you can catch typos and confirm you're assigning the right person. Non-existent accounts are rejected before any seat is used.</p>
<h2>Search when adding projects</h2>
<p>The Add Projects page now has a search box that filters across all accessible repositories server-side, so you no longer have to page through every repo to find one in a large Workspace.</p>
<h2><code>--skip-source-fetch</code> for <code>qlty coverage publish</code></h2>
<p><code>qlty coverage publish</code> now accepts <code>--skip-source-fetch</code>, matching <code>qlty check</code> and <code>qlty fmt</code>. When set, the command skips fetching remote sources and falls back to the default configuration if a source is not cached locally. See <a href="https://docs.qlty.sh/cli/commands/coverage-publish">coverage publish</a> for details.</p>
<h2>VB.NET maintainability analysis</h2>
<p>The Qlty CLI now analyzes <code>.vb</code> files for maintainability — complexity, duplication, and code smells — with VB.NET's case-insensitive member semantics handled correctly.</p>
<h2>Scala maintainability analysis</h2>
<p>The Qlty CLI now analyzes Scala (including Scala 3) source files for maintainability — complexity, duplication, and code smells.</p>
<h2>Knip honors <code>.qlty/configs/</code></h2>
<p>Fixed Knip not picking up a configuration file placed under <code>.qlty/configs/</code> in nested-package layouts. Qlty now passes the config path to Knip explicitly.</p>
<h2>RuboCop <code>AllCops: Exclude</code> now respected</h2>
<p>Qlty now passes <code>--force-exclusion</code> to RuboCop, so <code>AllCops: Exclude</code> patterns in your <code>.rubocop.yml</code> are honored even though Qlty invokes RuboCop with explicit file targets.</p>
<h2>editorconfig-checker findings no longer dropped</h2>
<p>Fixed a bug where <code>editorconfig-checker</code> results were silently discarded when the tool reported a <code>-1</code> line number for an issue it couldn't locate. All findings are now reported.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[June 2, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#june-2-2026</link>
            <guid isPermaLink="false">e88c7838a2b32533</guid>
            <category><![CDATA[CLI]]></category>
            <category><![CDATA[Coverage]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Verified CLI downloads in GitHub Actions</h2>
<p>The Qlty GitHub Actions now verify the Qlty CLI's Sigstore attestation before running it. Each action checks the downloaded archive against its signed provenance using the GitHub CLI, giving your workflows tamper-evident assurance that the binary came from Qlty. Verification is automatic and uses your existing <code>${{ github.token }}</code>.</p>
<p>See <a href="https://docs.qlty.sh/cli/integrity-verification">Integrity Verification</a> for details.</p>
<h2>More coverage formats in the GitHub Action</h2>
<p>The Qlty coverage GitHub Action now accepts <code>dotcover</code> and <code>xccov-json</code> as <code>format</code> values, so you can upload JetBrains dotCover and Xcode <code>xccov</code> JSON reports directly from your workflow without converting them first.</p>
<p>See <a href="https://docs.qlty.sh/coverage/generating-data">Generating Coverage Data</a> for details.</p>
<h2>Node 24 runtime for GitHub Actions</h2>
<p>The Qlty GitHub Actions now run on the Node 24 runtime, clearing the deprecation warning GitHub showed for the older Node 20 runtime and keeping the actions on a supported runtime ahead of GitHub's automatic migration.</p>
<h2>Windows support for the fmt action</h2>
<p>The Qlty <code>fmt</code> GitHub Action now runs on Windows runners in addition to Linux and macOS, so Windows-based CI pipelines can auto-format code with Qlty.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[April 15, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#april-15-2026</link>
            <guid isPermaLink="false">3b91d843cb4d5e99</guid>
            <category><![CDATA[CLI]]></category>
            <category><![CDATA[Cloud]]></category>
            <category><![CDATA[Coverage]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>C and C++ language support</h2>
<p>Qlty now provides maintainability analysis for C and C++. This includes complexity, duplication, and code smells, available in both the Qlty CLI and Qlty Cloud. See <a href="https://docs.qlty.sh/languages/c-cpp">C / C++</a> for details.</p>
<h2>Travis CI push branch detection</h2>
<p>Travis CI users no longer need to set the branch name manually when uploading coverage. The Qlty CLI now detects the branch automatically on Travis push builds, the same way it already does for other CI providers.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[April 9, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#april-9-2026</link>
            <guid isPermaLink="false">dd3340886e06c0f3</guid>
            <category><![CDATA[Plugins]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>editorconfig-checker plugin</h2>
<p>We've added a plugin for <a href="https://github.com/editorconfig-checker/editorconfig-checker">editorconfig-checker</a>, which verifies that your codebase follows the rules defined in <code>.editorconfig</code>.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[March 24, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#march-24-2026</link>
            <guid isPermaLink="false">a29979e807e610d5</guid>
            <category><![CDATA[Plugins]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Spectral plugin</h2>
<p>We've added a plugin for <a href="https://github.com/stoplightio/spectral">Spectral</a>, a linter for OpenAPI and AsyncAPI specifications.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[March 18, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#march-18-2026</link>
            <guid isPermaLink="false">12991fc36391b2ee</guid>
            <category><![CDATA[Plugins]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>golangci-lint v2 support</h2>
<p>The Qlty plugin for <a href="https://golangci-lint.run/">golangci-lint</a> now supports the v2 output format in addition to v1, so you can upgrade golangci-lint without losing report parsing.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[March 17, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#march-17-2026</link>
            <guid isPermaLink="false">a46cd3e0f889fac1</guid>
            <category><![CDATA[CLI]]></category>
            <category><![CDATA[Coverage]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Client-side coverage summing</h2>
<p>The Qlty CLI can now sum multiple coverage reports on the client before upload, complementing our existing server-side coverage merging. This is useful in CI workflows that already collect multiple coverage files on a single machine.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[March 5, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#march-5-2026</link>
            <guid isPermaLink="false">193da720e13b5310</guid>
            <category><![CDATA[Cloud]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Resync renamed repositories</h2>
<p>When a GitHub repository is renamed, you can now click a <strong>Resync</strong> button on the Add Project page to update Qlty's reference to the new repository name, keeping the Project's existing history and settings instead of having to re-add it from scratch.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[February 14, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#february-14-2026</link>
            <guid isPermaLink="false">7391356c19687af4</guid>
            <category><![CDATA[CLI]]></category>
            <category><![CDATA[Plugins]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>Python 3.13+ support</h2>
<p>The Qlty CLI now supports multiple Python runtime releases, enabling Python 3.13 and newer for plugins that require recent Python versions.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[February 5, 2026]]></title>
            <link>https://docs.qlty.sh/changelog#february-5-2026</link>
            <guid isPermaLink="false">a8aad1db900bc526</guid>
            <category><![CDATA[CLI]]></category>
            <pubDate>Mon, 17 Aug 2026 21:11:46 GMT</pubDate>
            <content:encoded><![CDATA[<h2>On-demand source fetching</h2>
<p>You now have precise control over when private sources are loaded — useful in offline or air-gapped environments, and for pre-fetching sources once in CI before running multiple analyses. A new <code>qlty sources fetch</code> command fetches the sources defined in <code>qlty.toml</code> without running analysis, and a new <code>--skip-source-fetch</code> flag tells <code>qlty check</code> and <code>qlty fmt</code> to use what's already on disk.</p>]]></content:encoded>
        </item>
    </channel>
</rss>