Seat-based licensing
June 12, 2026 Qlty Cloud now licenses Workspaces by seats instead of active contributors. A new Seat Management settings page lets admins assign seats to contributors and see how many are in use. See Seats for details.Verified seat assignment
June 12, 2026 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.Search when adding projects
June 12, 2026 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.--skip-source-fetch for qlty coverage publish
June 12, 2026
qlty coverage publish now accepts --skip-source-fetch, matching qlty check and qlty fmt. When set, the command skips fetching remote sources and falls back to the default configuration if a source is not cached locally. See coverage publish for details.
VB.NET maintainability analysis
June 12, 2026 The Qlty CLI now analyzes.vb files for maintainability — complexity, duplication, and code smells — with VB.NET’s case-insensitive member semantics handled correctly.
Scala maintainability analysis
June 12, 2026 The Qlty CLI now analyzes Scala (including Scala 3) source files for maintainability — complexity, duplication, and code smells.Knip honors .qlty/configs/
June 12, 2026
Fixed Knip not picking up a configuration file placed under .qlty/configs/ in nested-package layouts. Qlty now passes the config path to Knip explicitly.
RuboCop AllCops: Exclude now respected
June 12, 2026
Qlty now passes --force-exclusion to RuboCop, so AllCops: Exclude patterns in your .rubocop.yml are honored even though Qlty invokes RuboCop with explicit file targets.
editorconfig-checker findings no longer dropped
June 12, 2026 Fixed a bug whereeditorconfig-checker results were silently discarded when the tool reported a -1 line number for an issue it couldn’t locate. All findings are now reported.
Verified CLI downloads in GitHub Actions
June 2, 2026 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${{ github.token }}.
See Integrity Verification for details.
More coverage formats in the GitHub Action
June 2, 2026 The Qlty coverage GitHub Action now acceptsdotcover and xccov-json as format values, so you can upload JetBrains dotCover and Xcode xccov JSON reports directly from your workflow without converting them first.
See Generating Coverage Data for details.
Node 24 runtime for GitHub Actions
June 2, 2026 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.Windows support for the fmt action
June 2, 2026 The Qltyfmt GitHub Action now runs on Windows runners in addition to Linux and macOS, so Windows-based CI pipelines can auto-format code with Qlty.