Repository navigation
Releases
1.12.0.17622
SonarQube CLI v1.12.0
This release redacts secrets instead of blocking them for Copilot and Codex, extends import support to SonarQube Server, previews sonar init (Alpha) for guided project setup, and includes a range of bug fixes and security hardening.
Features
- Secrets redacted instead of blocked (Copilot and Codex): A secret in your session no longer stops your work. SonarQube masks it, tells the agent it was redacted, and the session continues. It covers prompts in Copilot and file reads in Codex. Anything that can't be masked safely is still blocked.
sonar importon SonarQube Server: Import GitHub, GitLab, Bitbucket Cloud, Bitbucket Server, and Azure DevOps repositories onto SonarQube Server.sonar linkproject picker: Runningsonar linkwithout a project key now shows an interactive project picker instead of failing.sonar auth logout --server <url>: Removes the saved connection and its keychain entry for a specific server URL, including inactive connections.- Architecture findings and filtering (SonarQube Cloud only):
sonar architecture findingsreads architecture deviations, flaws, and smells from existing analysis results. Current architecture dependency views can now be filtered by source/destination subtree and paginated. sonar init(Alpha): Go from zero to your first analysis in one guided command. It connects to SonarQube, sets up your project (import a repository, link an existing project, or start unbound), runs a first scan, and offers to set up your IDE or agent integrations.
Bug Fixes
- Server trust prompt: The "Connect to:
<url>?" confirmation insonar auth loginnow defaults to No, so a server URL taken from repository files is not accepted by accident. - Secrets scanner: Filenames starting with
-(e.g.--help) can no longer change scanner options, and timeout errors now give actionable guidance and advise against scanning entire repository trees. - Proxy and TLS:
SONAR_NO_PROXYexclusions are now respected over genericHTTP_PROXY/HTTPS_PROXYvariables. Feature-flag retrieval now honors the CLI's proxy, custom CA, and client-certificate settings. - Dependency installation: Managed executables such as
sonar-secretsare no longer treated as installed before signature verification completes, and concurrent installers now coordinate correctly. - Hook permissions: Reinstalling a managed Git hook now restores missing executable permissions on POSIX systems. Git silently ignored non-executable hooks.
- Integrations: The YAML adapter no longer overwrites or deletes files that contain malformed YAML.
- Agentic analysis: The default analysis now works before the first Git commit.
sonar updatePATH message: The CLI no longer asks you to open a new terminal or exportPATHwhen the install directory is already onPATH.- Architecture exports: Intended architecture exports from a different project are now rejected with a clear error.
Miscellaneous
- Updated
node-forgeto v1.4.3 andfollow-redirectsto v1.16.2 (security fixes). - The MCP server now receives proxy and TLS JVM settings through a temporary read-only argument file, which is cleaned up on exit.
- Internal refactors and dependency bumps.
1.11.0.16877
SonarQube CLI v1.11.0
This release expands monorepo support across analysis features, introduces architecture commands, adds new multi-project linking tools, and rounds out several agent integrations — alongside a range of bug fixes and security updates.
Features
- Devin and Pi integrations: New
sonar integrate devinandsonar integrate picommands set up secrets scanning, Vortex analysis and context augmentation, and the SonarQube MCP server. - OpenCode 2.0 support:
sonar integrate opencodenow installs plugins compatible with OpenCode 2.0. - Monorepo support for analysis: SCA dependency analysis, Vortex code analysis, and Vortex context augmentation now all work correctly in monorepos. Each affected project is analyzed independently, and ambiguous project resolution produces clear guidance to re-run from the correct subdirectory.
sonar link list: New command to look up which SonarQube project covers a given file or directory path, with pagination support — useful in large monorepos with many linked projects.- Link multiple projects with
sonar link:sonar linkcan now create and update multi-project configurations, letting you map several subdirectories to different SonarQube projects without editing.sonar-config.jsonmanually.
- Architecture commands: New
sonar architecturecommands let you read current and intended project architecture and update intended architecture models. An architecture skill installer is also available in Beta. sonar auth org: New command to switch the active SonarQube Cloud organization without logging out and back in. When no organization key is provided, an interactive list is shown. (sonar auth login --orgpoints to this command when reusing a stored token.)- MCP container networking for self-hosted SonarQube: Set
mcp.container.autoNetwork=trueto automatically configure container access to SonarQube Server running onlocalhost. Disabled by default. - Vortex context failure reporting: When the SessionStart hook cannot inject Vortex context (e.g., because the project cannot be resolved), the failure and discovery diagnostics are now reported clearly instead of silently skipped.
Bug Fixes
- Env-var auth no longer overwrites saved login: Running a command with
SONARQUBE_CLI_TOKEN/SONARQUBE_CLI_SERVERenvironment variables no longer replaces the connection saved bysonar auth login. The stored login is preserved for subsequent commands that do not use env vars. - Stored token scoped to server URL: The CLI no longer reuses a stored token for a different scheme, port, or base path on the same hostname. The token is now matched against the full recorded server URL.
- Interactive prompts cancelled cleanly on closed stdin: Interactive prompts (e.g., on Windows) no longer freeze the terminal when stdin is closed — they are cancelled immediately.
- Self-update compatibility: Fixed a crash in older CLI processes that access telemetry state after an update.
- Vortex wording: Revised agentic analysis instructions to reduce the risk of agents interpreting them as a prompt injection attempt.
- Concurrent state-file writes: Multiple CLI processes (hooks, MCP server, telemetry, parallel integrations) can no longer corrupt or reset
state.jsonthrough simultaneous writes. sonar apierror messages: API error responses from SonarQube are now surfaced in full rather than showing only the HTTP status code.- Organization conflict detection: Commands such as
sonar list issues,sonar remediate, andsonar analyze dependency-risksnow detect when the active organization does not match the project and fail with a clear error instead of silently returning wrong results. - Git secrets scanning: Pre-commit and pre-push hooks now block the operation when Git cannot list the files to scan, preventing scanning from being silently skipped.
Miscellaneous
- Standalone CLI binaries no longer automatically load
.envorbunfig.tomlfiles from the working directory to prevent potential security risks. - Internal refactors to support multiple project bindings in the project model and declarative feature availability in
sonar integrate. - Bundled Context Augmentation upgraded to 0.24.0.
1.10.1.16776
SonarQube CLI v1.10.1
This is a maintenance release with a security update.
Security
- Internal dependency updates including the Bun runtime, SCA scanner, secret analysis engine, and context augmentation components.
1.10.0.16040
SonarQube CLI v1.10.0
This release introduces the new sonar integrate opencode command, a full sonar config command suite, sonar list org, and the sonar allowlist secrets command group, alongside several bug fixes and polish improvements.
Features
- OpenCode integration:
sonar integrate opencodeinstalls secrets scanning hooks for OpenCode — scanning files on read and prompts on submission — and configures the SonarQube MCP server automatically. Agentic analysis (per-edit quality scanning) and context augmentation skills are also configured as part of the integration. sonar configcommand suite: A new set of commands lets you get, set, unset, and list persistent CLI configuration options (proxy, CA certificate, mTLS client certificate, log level, and more). Sensitive values are stored in the OS keychain and redacted in output. Settings follow the precedencesonar-env > stored config > environment variable.sonar config set <key> <value>— store a configuration valuesonar config get <key>— read a stored value (sensitive values are shown as asterisks)sonar config unset <key>— remove a stored valuesonar config list— print every supported key with its current value or(not set)
sonar list org/sonar list orgs: Lists the organizations available to the authenticated user, with support for--format jsonand the default table format.sonar allowlist secretscommand group: Surfaces the secrets scanner's allowlist management directly through the CLI, so developers can resolve false positives without invoking a separate binary.sonar allowlist secrets show— display the current allowlistsonar allowlist secrets add— add a key to the allowlist (with a TTY safety gate)sonar allowlist secrets remove <key>— remove a specific keysonar allowlist secrets clear [--force]— clear the entire allowlist
- Pre-push hook scans commit contents: The secrets pre-push git hook now scans the actual contents of the pushed commits rather than the working tree, giving accurate results when pushing branches other than the one currently checked out.
- Config visibility improvement:
sonar config getnow displays unset values and hidden/sensitive values in grey, with sensitive values shown as asterisks rather than the literal text(hidden). - Telemetry consent via config store: Telemetry and stats opt-in/out settings are now managed through
sonar config set/getrather than the dedicatedsonar config telemetryandsonar config statssubcommands, which have been removed.
Bug Fixes
- Broken pipe crashes: Fixed uncaught
EPIPEerrors that caused the CLI to crash silently when output was piped to a program that closed early (e.g.,| head) or when a child process exited before all input was written. - Windows agent stdout held open: Fixed an issue on Windows where the telemetry flush worker kept the agent's stdout open, causing Claude Code to discard hook output and start subagents without SonarQube guidance.
- Keychain-unavailable environments:
sonar contextand other commands now survive gracefully in environments without a system keychain (containers, CI, Factory workspaces), and provide accurate remediation advice instead of directing users to installlibsecret. - Telemetry flush worker on Linux update: Fixed a crash during
sonar updateon Linux where the telemetry flush worker attempted to spawn the replaced binary after the update completed, resulting in anENOENTerror.
Miscellaneous
- Updated bundled SonarText (secrets scanner) to 2.53.0.13730, which improves CA certificate handling and signs macOS and Windows artifacts.
- Internal refactoring of organization resolution logic into a shared module in preparation for an upcoming organization-switching command.
- Removed dead global-hook detection code from agent integrations.
- Moved the telemetry ingest key to a dedicated module to prevent the secrets scanner from blocking reads of frequently-edited source files.
- Tagged Sentry error reports with the CLI release version to improve stack trace readability and regression tracking.
- Dependency updates:
js-yaml,@sentry/bun,typescript-eslint, andsonar-context-augmentation.
1.9.0.15656
SonarQube CLI v1.9.0
This release ships new commands such as sonar import or sonar stats command, supports global integrate by default, features a batch of quality-of-life improvements across commands and output, and several bug fixes and security hardening items.
Features
sonar integratenow operates at the global level: The integration framework has been redesigned to configure integrations globally across all projects rather than per-project. This unifies configuration, reduces duplication, and simplifies management. On first run of v1.9.0, an automatic migration cleans up any existing project-level integration artifacts and moves them to the global configuration. If the project key cannot be auto-discovered, run sonar link in your project directory to connect it to SonarQube.sonar importis now available in Open Beta: Thesonar importcommand allows to import repositories from a connected DevOps platform into SonarQube.sonar statscommand (Alpha): A newsonar statscommand displays a local summary of your SonarQube CLI usage — commands run, analyses performed, and more. Supports--jsonoutput and a--sincewindow (7d, 14d, 30d, all). Raw event data older than one year is automatically purged while aggregates are retained for all-time reporting. Stats collection is controlled by its own dedicated consent flag, independent of the general telemetry opt-in, since this data is consumed locally only.sonar update statussubcommand:sonar update --statushas been promoted to a propersonar update statussubcommand for consistency withsonar auth statusandsonar system status. The new subcommand also gains--formatsupport for JSON output.sonar auth login --with-token: You can now pass a token directly tosonar auth loginvia the--with-tokenflag, enabling non-interactive authentication flows.- Consistent
--formatflag: All data commands now accept a uniform--formatflag for JSON output. - GitLab CI custom job template:
sonar admin onboard-ci gitlabnow accepts a--job-template <file>flag, letting you inject your own YAML job definition instead of the default template. - Organization membership mismatch warning:
sonar auth statusnow reports a clear diagnostic when your token has no membership for the configured organization, instead of silently showingConnectedwhile features like Vortex are unavailable.
Bug Fixes
- Pre-push hook scan scope: Fixed an issue where the pre-push hook defaulted to a full repository scan when it should have scanned only the changed files.
- Vortex keep/remove decision: Fixed a bug where declining to keep an already-installed Vortex on re-run would remove the top-level feature but silently reinstall it because sibling hook features (e.g. Claude's
PostToolUsedispatch, Codex's SQAA subfeature) re-derived the install decision independently. All Vortex-gated features now agree on a single keep/remove answer. - Server URL validation: Server URLs are now validated to confirm they are actually URLs, not just checked for the absence of line breaks.
- Line break rejection: Server URLs and project keys containing line breaks are now rejected at resolution time — at
sonar auth login, via environment variable, or via--project— with a clear error pointing at the correct fix. - Error logging: Fixed a bug where swallowed errors were logged as
{}in the file log instead of their actual cause, making several silent failure paths undiagnosable. - No-project-key messages: Messages shown when no project key is configured now point users at
sonar link <projectKey>instead of the outdatedsonar-project.properties/.sonarlintreferences. - Integration copy and warnings: Clarified several integration and migration messages that described what went wrong but not what to do — hook-conflict warnings and migration notices now include actionable next steps.
Security
- OAuth loopback hardening: The OAuth callback during
sonar auth loginnow requires both127.0.0.1and::1to bind each candidate port, preventing a local process from occupying the IPv6 loopback port and intercepting the OAuth token on systems where browsers prefer IPv6 forlocalhost. - Authentication callback hardening: Tightened browser authentication callback acceptance and state validation to address issues identified by SonarQube analysis.
Miscellaneous
- Organization details are now resolved through the public organizations API rather than an internal, undocumented endpoint.
- Crash reports sent to Sentry now route through the configured proxy and CA certificate, restoring error visibility for installations behind mandatory corporate proxies.
- The
CliCommandExecutedtelemetry event now captures which flags and options were used in each invocation. - Internal refactors and dependency bumps.
1.8.0.5274
SonarQube CLI v1.8.0
This release significantly expands the sonar quality-gate status command with drill-down enrichment, introduces sonar link for manual project binding, and brings several quality-of-life improvements across issue listing, authentication, and agentic integrations.
Features
- Quality Gate drill-down enrichment:
sonar quality-gate statusnow supports--category <coverage|duplications|issues|security|dependency-risks>and--top <N>flags to show the worst-N files or issues behind each failing condition, making it actionable at a glance.- Coverage: shows the worst files by coverage value for failing coverage conditions.
- Duplications: shows the worst files by duplication metric for failing duplications conditions.
- Issues, Reliability & Maintainability: shows the worst bugs, code smells, and violations for failing issue-count and rating conditions.
- Security: shows the worst vulnerabilities for failing security conditions.
- Dependency Risks: shows the worst SCA dependency risks (malware, prohibited licenses, vulnerabilities) for failing SCA conditions.
- Quality Gate file drill-down:
sonar quality-gate status <file>narrows the quality gate view to a single file or directory, showing only the conditions and issues relevant to that path. Use--allto also show passing conditions. - PR auto-resolution:
sonar quality-gate statusnow automatically resolves the pull request for the current branch via SonarQube's API when neither--branchnor--pull-requestis specified. - Issue filtering by file or directory:
sonar list issuesnow accepts a--file <path>flag to scope results to a single file or directory without going through the quality gate. - Open/confirmed issues by default:
sonar list issuesnow returns only open and confirmed issues by default, matching the most common use case. Previously no status filter was applied. sonar link <project-key>command: new command that writes a local binding file for the current directory, letting you manually associate a repository with a SonarQube project key when auto-discovery cannot find one.- Auth warning on login with env vars:
sonar auth loginnow displays a clear warning when authentication environment variables are already set, explaining that they will continue to take precedence and thatsonar auth statuscan be used to inspect the current connection. - Agentic analysis quieted when no project is configured: when no project is linked,
sonar analyze agenticno longer emits a distracting skip message on every turn; the agent is instructed to discard the output silently. - Vortex (Agentic Analysis) now works at global scope:
sonar integrate claude -g(and other global integrations) now installs Vortex analysis hooks correctly, without requiring a project directory. Project resolution happens at runtime. - Context Augmentation delivered via session-start hook: Vortex context is now delivered through the agent's session-start hook rather than a static
SKILL.mdfile, removing the project-scope constraint and leaving no stale file on disk from previous installs. - Onboard CI GitLab (alpha): added
sonar admin onboard-ci gitlabcommand for setting up GitLab CI integration. - Successful import links to project list: after a successful project import, the CLI now links to the project list page rather than the (not-yet-ready) dashboard.
Bug Fixes
- Issue search parameters fixed:
sonar list issueswas sending incorrect query parameters to the SonarQube API — on SonarQube Cloud the project filter was silently dropped, and on SonarQube Server the new-code period filter was a no-op since Server 10.0. Both are now fixed. The minimum supported SonarQube Server version is raised to 25.1. - Change-set path validation: paths in the change set are now validated against the repository boundary before file inspection, preventing traversal outside the repository root.
Miscellaneous
- Continued foundational work on the agentic integrations architecture: centralized auth resolution,
agent-session-starthook handler, and MCP configuration test coverage for global-scope installs. - Extensive internal refactoring of the HTTP client layer (Result monad propagation, domain API clients,
SonarHttpClientextraction) and the console/UI wrapper, with no user-visible behavior change. - Internal dependency bumps and code health improvements.
1.7.0.4638
SonarQube CLI v1.7.0
This release introduces the sonar quality-gate command for checking your project's Quality Gate status from the terminal, improves git hook chaining, fixes several bugs, and includes a range of internal improvements.
Features
- Quality Gate status command: New
sonar quality-gate statuscommand (also accessible assonar qg status) displays your project's Quality Gate verdict directly from the terminal. ReportsOK,ERRORwith a list of failing conditions, orNot computedwith a hint to runsonar analyze. Exits with a distinct code for each outcome. sonar contextis now stable: Thesonar contextcommand is promoted from Open Beta to stable — the[BETA]label and beta warning are removed, and the command appears in root help like any other GA command.- Global git hook chaining: When
sonar integrate gitis installed globally (viacore.hooksPath), Sonar's hook scripts now detect and chain to any pre-existing local.git/hooks/<name>script in each repository, so hand-written hooks and other hook frameworks are no longer silently bypassed. - Vortex entitlement check on SonarQube Server: The CLI now queries the SonarQube Server CAG Hub to determine whether Vortex (Agentic Analysis) is licensed, rather than always returning
not_applicablefor non-Cloud connections. - Staged command options: Command options can now be individually marked as alpha or beta, respecting the same visibility and entitlement rules as staged commands.
Bug Fixes
- MCP config on Windows:
sonar integratecommands no longer writesonar.exeas the MCP server command on Windows. The generated.mcp.jsonnow usessonar, which works cross-platform and is safe to commit in mixed-OS teams. - Custom
SONAR_USER_HOMEin MCP config: WhenSONAR_USER_HOMEis set to a non-default path,sonar integratenow includes it in the generated MCP server entry so the MCP process can find CLI state and authenticate correctly — previously users had to hand-edit the config. - Claude Code hook path anchoring: Project-scope Claude Code hook commands are now anchored to
${CLAUDE_PROJECT_DIR}instead of the current working directory, preventing hook failures when the working directory diverges from the project root (e.g. in worktrees). - Hook stdin listener leak on timeout: A timed-out stdin read in hook scripts no longer keeps the process alive indefinitely; listeners are now properly cleaned up so the process exits as expected.
- Binary install robustness: The CLI no longer fails a binary installation when the installed binary's version output doesn't match an expected format. The spawned binary is verified to exit successfully, but version-string parsing is no longer required.
- Shared binaries no longer deleted on feature removal: Removing an integration feature no longer deletes a shared binary (e.g.
sonar-secretsorsca-scanner-cli) that may still be in use by another flow such assonar analyze secrets. Previously this could trigger an unexpected re-download on next use.
Miscellaneous
- Internal telemetry improvements: agent session IDs are now resolved from agent-native environment sources and included in CLI telemetry events; the invocation ID is forwarded to Vortex analysis requests; telemetry emission is deferred to post-command processing for cleaner enrichment.
- Foundational work on unified project-key resolution and installed-agent discovery, supporting upcoming improvements to
sonar integrate. - Internal refactors and dependency bumps.
1.6.0.4255
SonarQube CLI v1.6.0
This release brings Vortex entitlement visibility into sonar system status, automatic cleanup of Vortex when entitlement is lost, and foundational work on the Private Beta command gating system.
Features
- Vortex status in
sonar system status: A new Vortex section now appears insonar system status, showing your current entitlement and usage state. Genuine entitlement loss is surfaced as an unhealthy status with a recommendation to re-enable Vortex or remove its integration; usage-limit exhaustion remains healthy. - Automatic Vortex uninstall on entitlement loss:
sonar integratenow automatically removes Vortex and its associated configuration when entitlement is genuinely lost, keeping your setup clean without manual intervention. - Improved secrets pre-push hook output: Output formatting for the secrets pre-push hook has been improved for better readability.
Miscellaneous
- Internal work on end-of-turn Vortex instructions for the Codex integration.
- Internal refactors and infrastructure improvements.
1.5.0.4158
SonarQube CLI v1.5.0
This release brings unified Vortex integration across all supported AI agents, improvements to sonar import, better error messaging for authentication, and several bug fixes.
Features
- Vortex integration for all agents:
sonar integratenow installs a unified Vortex feature (combining SonarQube Agentic Analysis and context augmentation) for Claude Code, Copilot, Codex, Cursor, and Antigravity — with a single entitlement check, a single prompt, and automatic migration of any previously installed separate SQAA/CAG features. - Claude Code context augmentation hooks:
sonar integrate claudenow installsPostToolUseandPostToolUseFailurehooks so Claude can forward relevant tool output for context augmentation. - Vortex entitlement awareness: The CLI now distinguishes genuine entitlement loss from usage-limit exhaustion when Vortex API calls are rejected, showing distinct, actionable messages for each case and throttling repeated entitlement-loss warnings.
- Keychain error messaging: When the system keychain is unavailable, the error message now mentions environment variable authentication as an alternative, including the relevant variable names.
- MDM deployment scripts: Reference scripts for enterprise MDM deployment are now published as part of the CLI repository.
Bug Fixes
- Telemetry proxy support: Telemetry events were bypassing configured proxy and TLS settings. They are now routed through the resolved network configuration, ensuring correct behavior in corporate proxy environments.
- Telemetry test isolation: Test runs were inadvertently sending fixture data to the production telemetry endpoint; this has been fixed.
Documentation
- Updated the README to include Codex, Cursor, and Antigravity in the list of supported AI agents.
- Made the CLI landing page mobile-responsive and updated the quickstart guide.
- Published sample telemetry events documentation for enterprise customers.
Miscellaneous
- Continued foundational work on the Vortex (formerly Agentic Analysis / Context Augmentation) product unification, including internal hook dispatch refactoring, a shared entitlement resolver, subfeature resource ownership, post-update migration logic, and allowlist-gating for context augmentation hooks.
- Extensive internal restructuring of the source tree (moving code under
src/core/,src/commands/, and related directories) to improve contributor ergonomics; no user-facing behavior changed. - Updated bundled
sonar-context-augmentationbinary to 0.19.0.3620. - Dependency updates including
@sonar/scan,js-yaml(security),eslint,typescript-eslint,@sentry/bun, and others.
1.4.0.3748
SonarQube CLI v1.4.0
This release brings enterprise network configuration support for the MCP server, several improvements to agentic workflows, expanded sonar import capabilities, and a collection of bug fixes.
Features
- MCP Server: Proxy, CA Certificate, and mTLS Support: The
run mcpcommand now forwards proxy settings, custom CA certificates, and mTLS configuration stored in the CLI to the MCP server container, enabling use in enterprise network environments. - MCP Server: WSL Container Runtime Support:
run mcpcan now detect and use container runtimes (e.g., Docker) running inside WSL on Windows systems. - Auto-detect Git Branch for Agentic Analysis:
sonar analyze agenticand the associated hooks now automatically detect the current git branch and pass it as context to SonarQube, improving analysis accuracy without requiring--branchto be specified manually. sonar updateCommand: Introducedsonar updateas the new name forsonar self-update. The old command still works but prints a deprecation warning pointing to the new name.- Agent-Friendly Syntax Hints: Interactive prompts now display the equivalent non-interactive flag syntax before prompting, helping AI agents discover the correct flags instead of getting stuck waiting for input.
- Hook Failures on Missing Auth or Binary: Pre-commit/pre-push hooks no longer fail silently when the user is unauthenticated or the secrets scanner binary is missing — they now surface a clear error so the problem is immediately visible.
- Git Worktree Support for Agentic Integrations: Project key resolution for
sonar analyze agenticand the Code Augmentation binary now works correctly when operating from a git worktree. sonar api: Automatic SonarQube Cloud API Host Rewriting: When connected to SonarQube Cloud,sonar apinow automatically rewrites/api/v2/...paths to the correct Cloud API host, fixing failures against endpoints such as SCA issue releases.analyze dependency-risks: The incorrect beta label has been removed from theanalyze dependency-riskscommand.
Bug Fixes
- State File Corruption on Read Failure: A failed or corrupt read of the internal state file no longer silently overwrites it with defaults, which previously caused unexpected logouts.
- Secrets Hook State Written Even When Declined: Fixed an issue where declining the secrets scanning hooks prompt during
sonar integrate claudestill recorded the hooks as installed in internal state. - Hook Command Paths with Spaces: Hook command paths written to agent configuration files (e.g.,
.claude/settings.json) are now properly quoted, fixing failures when the project or home path contains spaces or other shell metacharacters. - Unknown Subcommands for
analyze: Runningsonar analyze <unknown>now reports the unrecognized subcommand clearly instead of showing a misleading "too many arguments" error. - Entitlement Check for
sonar integrate: Integration setup now correctly distinguishes between not being entitled to a feature and having exceeded consumption limits, preventing incorrect failures at startup.
Installation & Distribution
- Homebrew and Mise Documentation: The README and documentation website now mention Homebrew and Mise as supported installation methods.
- macOS Signing: The macOS binary is now signed under the updated Apple Developer ID for SonarSource Sàrl.
Miscellaneous
- Continuation of the foundational work for the bulk project onboarding (creation of SonarQube project from the selected repository, concurrent import of repositories).
- Updated the Context Augmentation binary to version 0.18.0.