Skip to content

Releases: SonarSource/sonarqube-roslyn-sdk

4.0

21 May 07:42
bacf199
Compare
Choose a tag to compare

This release fully supports the most recent version of SonarQube, 10.5.1, as of this release! And analyzers based on Roslyn up to 4.9.2.

⚠️ Please note: This SonarRoslynSDK version is only compatible with SonarQube versions 9.9 and above.

Improvements

  • #204 - Update Roslyn dependency version
  • #209 - Display a help when no argument provided
  • #100 - Add VB.NET support
  • #128 - Fix issue with jar files not properly unzipping on Linux
  • #215 - Update template plugin to 1.3.0.1139
  • #203 - Improve failure message when no analyzers found

Full Changelog: 3.1...4.0

v3.1

20 Oct 12:50
Compare
Choose a tag to compare

Update Roslyn and NuGet.CommandLine versions

Improvement

  • #191 - Update to latest Roslyn version (v4.3.1)

Security

  • #178 - Stop using vulnerable NuGet.CommandLine package (CVE 2022-30184)
  • #190 - Stop using vulnerable NuGet.CommandLine package (CVE 2022-41032)

v3.0

17 Nov 21:27
Compare
Choose a tag to compare

Support Roslyn v4.0

Improvement

  • #123 - Support analyzers created using VS2022

2.0

08 Aug 18:51
10a1c69
Compare
Choose a tag to compare
2.0

Bug

  • #74 - Remove usage of deprecated APIs

Improvement

  • #76 - Handle versions of Roslyn greater than v1.0
  • #77 - Upgrade to NuGet 4.7
  • #87 - Drop support for SQALE xml file
  • #89 - Allow the user to customize the rules.xml file
  • #92 - Update assembly version for v2.0 release

1.0

09 Mar 10:16
Compare
Choose a tag to compare

1.0-RC1

04 Mar 16:16
Compare
Choose a tag to compare

Initial review release

17 Feb 09:09
Compare
Choose a tag to compare
Pre-release

Supports generating a valid SonarQube plugin for a Roslyn analyser provided as a NuGet feed
Analyzers can use Roslyn v1.0 or v1.1.
Requires SonarQube Scanner for MSBuild v2.0 and C# plugin v4.5 or higher

Known limitations:

  • will not generate plugins for NuGet plugins that have RequireLicenseAcceptance set to true (still need to clarify the legal position here)
  • no opportunity to customise the generated jar (e.g. to provide richer rule descriptions or remediation costs)