SonarLint for IntelliJ v10.10 delivers performance enhancements and new rules for JS.

This release sees various items designed to improve performance and optimize memory use.

Plus

• 6 new rules to help you write clean JS code
• Updated SonarIaC analyzer delivering support for detecting Micronaut configuration issues in YAML & properties files

Find more details in our release notes and community announcement.

SonarLint for IntelliJ v10.9 brings support for identifying security flaws in Helm files.

SonarLint can now identify security flaws in Helm files within the Kubernetes analysis. This is designed to help cloud native developers using Helm charts to design and implement secure cloud architecture.

In addition:

• 7 new rules for writing C++23 code
• Improved Rider analysis by making sure to include all the files of a solution.

Find more details in our release notes and community announcement.  

SonarLint for IntelliJ v10.7 delivers added value for users of SonarCloud.

With the new Open in IDE button in SonarCloud you can now open any issue you are investigating in SonarCloud directly into IntellliJ with a single click. SonarLint will automatically open the correct file and take you to the line of code containing the issue.

Plus, we have enabled the Clean as You Code methodology, allowing you to focus only on issues in your new code. This incremental approach empowers developers to take ownership of all new code and tackle overall technical debt in a manageable and sustainable manner.

In addition:

• Improved analysis capabilities for Python and Java with advanced issue detection when in connected mode to either SonarQube or SonarCloud

Find more details in our release notes and community post.

SonarLint for IntelliJ 10.6 adds support for CLion Nova and the Resharper C++ language and improves Connected Mode setup for C# projects in Visual Studio and Rider IDEs. You can learn more about how to share configurations between IDEs here.

• For Python, we added 5 rules which mainly focus on the machine learning library Scikit-Learn.
• C# received 7 new rules.

Also of note, To enforce security connection in the IDE as well as on SonarCloud and SonarQube, we are deprecating the authentication with login/password for the Connected Mode. We highly recommend using token authentication instead.

Discover more with our release notes and community announcement. 

SonarLint for IntelliJ 10.5 enables enhanced collaboration by introducing a sharing Connected Mode setup among contributors and new rules.

• For Java, we introduced new Java 21 rules and new sustainability rules
• Python received 14 new rules (4.16 and 4.17)
• Improved Javascript/Typescript with 4 new accessibility rules

Also of note, we are dropping support of NodeJS v16.

Discover more with our release notes and community announcement. 

SonarLint for IntelliJ v10.4 introduces a new architecture that relocates the SonarLint business logic from the IDE to a background process and enhances IDE responsiveness.

In addition:

• We’ve added 17 new rules for accessibility in HTML.
• We improved the top dismissed JS/TS rules and added one rule (S2004).
• We fixed 13 false positive rules and added 2 new quick fixes for Python.

Find more details in our release notes and community announcement.

SonarLint for IntelliJ v10.3 enhances the combined power of SonarLint and SonarQube while streamlining the setup process.

Now, a one-click connection setup and project binding option will be shown to a SonarLint for IntelliJ developer utilizing the SonarQube “Open in IDE” button to investigate an issue directly in their IntelliJ IDE. This functionality, which requires SonarQube v10.4, assists developers in rapidly examining and resolving issues using SonarLint directly in their IntelliJ IDE.

Plus, with their SonarLint for IntelliJ v10.3 connected to SonarQube v10.4, developers can now detect custom secrets in their code, directly in their IDE. Using custom rules based on secret patterns defined in SonarQube this allows developers to spot secrets before they can be leaked into repositories. (Requires SonarQube Enterprise or Data Center Edition).

Also using connected mode to SonarCloud or SonarQube v10.4, it is possible to mark an issue as “Accepted”. This results in the unresolved issue becoming part of the project’s technical debt.

In addition:

• 8 new Kubernetes rules
• 9 new C++ rules to help with MISRA 2023

Find more details in our release notes and community announcement. For more details on how to set up connected mode check here.

SonarLint for IntelliJ v10.2 introduces a set of rules to help you correctly configure your Kotlin DSL build script, acknowledging that Kotlin DSL is now the default for new Gradle builds.

Find more details in our release notes and community announcement.

SonarLint for IntelliJ v10.1 delivers new rules across a variety of languages, plus insights into the additional team benefits available when using SonarLint in connected mode with SonarCloud and SonarQube.

New rules:

• 9 new Java rules to help you avoid common pitfalls with Spring Boot
• 6 new rules to avoid adding bugs in Kotlin code
• Support for .Net 8 and C# 12
• Support for Python 3.12 syntax, along with 4 new rules related to Python 3.12 features
• 17 new JavaScript rules for JSX

Find more details in our release notes and community announcement.

SonarLint for IntelliJ v10.0 brings additional team benefits when using SonarLint in connected mode to SonarCloud and SonarQube.

Now, with SonarQube v10.3, you can open any issue you’re investigating in SonarQube directly into the IDE, with just a click of a button, thanks to connected mode. This allows you to leverage SonarLint’s dataflow navigation, rule descriptions, and quick fixes for efficient issue investigation and resolution.

Plus, when using connected mode to SonarCloud, any issue or status change (e.g. Won’t Fix, False Positive) made in SonarCloud will be instantly synchronized to your IDE, ensuring you can focus on relevant issues.

Also:

• 6 Java rules dedicated to the Spring framework
• 5 Python rules 2 for the Pandas library
• Many new JavaScript and TypeScript rules for React

Lastly, the whole Sonar ecosystem will soon require Java 17 as a minimal runtime to analyze your projects. To satisfy this requirement in SonarLint for IntelliJ, we’re raising the minimum IDE version to IntelliJ 2022.3.1.

Find more details in our release notes and community announcement.