JetBrains Qodana 2026.1 Launches: C/C++ Now Production-Ready, Rust Enters Early Access
Breaking: Qodana 2026.1 Ships with Stable C/C++ Linter and Rust EAP
JetBrains today released Qodana 2026.1, its static analysis platform, marking a major milestone for native code development. The C/C++ linter has graduated from Early Access Program (EAP) to general availability, while a new Rust linter enters its first EAP. Additionally, the update introduces a fresh set of inspections targeting Kotlin, Python, and C#.

“We’ve seen strong adoption of Qodana for C/C++ since its preview last year,” said Anna Petrova, Senior Product Manager for Qodana. “Thanks to extensive community feedback, the linter is now hardened for production pipelines.”
Qodana for C/C++ Exits EAP
The C/C++ linter, first previewed in Qodana 2025.1, is now fully supported in CI/CD environments. Key improvements based on user feedback include:
- Build failure detection: Qodana now properly identifies CMake and other build system errors, helping teams diagnose issues faster.
- Configurable timeout: Large projects can set
qd.cpp.startup.timeout.minutesinqodana.yamlto prevent premature analysis termination. - Ignored cached configs: The
.ideafolder contents are now skipped, avoiding conflicts with local IDE instances.
JetBrains recommends cleaning cached build data and closing local IDEs before running Qodana to ensure accurate results. Full documentation is available on the C/C++ linter page.
Rust Linter Launches in EAP
The new Qodana for Rust EAP addresses the language’s explosive growth—over 2.5 million developers use Rust, and it has ranked as the most admired language on Stack Overflow for a decade. The EAP brings:
- 150+ inspections covering dead code, lifetime issues, unsafe code, and more, plus built-in
cargo checkandcargo clippyintegration. - Conditional compilation and feature gating support, including proc macros.
- Rust toolchain management via
rustupin the bootstrap block. - Multi-workspace support for monorepo setups.
“Rust teams building infrastructure and performance-critical systems need robust static analysis,” added Petrova. “This EAP gives them a head start on catching bugs before deployment.” The full inspection catalog is on Inspectopedia.

New Code Inspections Across Ecosystems
Version 2026.1 introduces targeted inspections for Kotlin, Python, and C#. One highlighted example is the “Suspicious ::java” inspection for Kotlin, which flags potential misuse of Java interop patterns that could lead to runtime errors. Python and C# inspections address common logic pitfalls in data processing and null safety.
Background
Qodana is JetBrains’ cloud-native static analysis platform, designed to catch code issues early in the development lifecycle. It integrates with major CI/CD systems and supports multiple languages. The 2026.1 release follows a year of C/C++ enhancements and responds to rising demand for Rust tooling.
What This Means
For development teams, the stable C/C++ linter removes a barrier to adopting automated static analysis for legacy and new C/C++ projects. The Rust EAP offers early access to an ecosystem that has long lacked a dedicated, commercial-grade linter from a major vendor. Combined with the new inspections, Qodana 2026.1 strengthens its position as an all-in-one code quality gate.
Developers can start using Qodana for Rust immediately via the EAP. The C/C++ GA is available through existing subscription plans. JetBrains encourages Rust users to provide feedback to shape the linter’s final release.
Related Articles
- Exploring Python 3.15.0 Alpha 2: Key Features and Developer Insights
- Python's Flexibility Comes at a Cost: Standalone App Bundling Remains a Persistent Challenge
- Microsoft Releases Earliest DOS Source Code to Public on Its 45th Birthday
- Mastering the Factory Method Pattern in Python: A Step-by-Step Guide
- Python 3.15.0 Alpha 6: A Developer Preview Packed with Performance Boosts and New PEPs
- Stack Overflow's 2008 Launch Revolutionized Developer Learning Overnight, Experts Say
- 10 Essential Insights into Agent-Driven Development with GitHub Copilot
- AGI Hopes Hinge on Transformer Models — But Critics Warn of a 'Waste of Resources'