From 9fa3da5f3fbb603e4ce79c942a82268f9a1a6c98 Mon Sep 17 00:00:00 2001
From: Felipe Zorzo <felipe.b.zorzo@gmail.com>
Date: Thu, 27 Jun 2024 21:29:50 -0300
Subject: [PATCH] build: Release 3.5.1

---
 README.md                           |  2 +-
 build.gradle.kts                    |  2 +-
 plsql-custom-rules/build.gradle.kts |  4 ++--
 plsql-custom-rules/pom.xml          |  2 +-
 template/changelog.tpl              | 13 +++++++++++++
 5 files changed, 18 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index e5a77dbb..b8039ad3 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ If you like to live on the bleeding edge, you can use the [latest development ve
 
 | ZPA version                                          | SonarQube version (min/max) |
 |------------------------------------------------------|-----------------------------|
-| 3.5.0                                                | 9.9 / 10.6                  |
+| 3.5.1                                                | 9.9 / 10.6                  |
 | 3.6.0 ([early-access][early-access], in development) | 9.9 / 10.7                  |
 
 ## ZPA Toolkit
diff --git a/build.gradle.kts b/build.gradle.kts
index f0406d63..272d23f8 100644
--- a/build.gradle.kts
+++ b/build.gradle.kts
@@ -32,7 +32,7 @@ allprojects {
     }
 
     group = "com.felipebz.zpa"
-    version = "3.6.0-SNAPSHOT"
+    version = "3.5.1"
 }
 
 subprojects {
diff --git a/plsql-custom-rules/build.gradle.kts b/plsql-custom-rules/build.gradle.kts
index 6f3d0978..dbfbf585 100644
--- a/plsql-custom-rules/build.gradle.kts
+++ b/plsql-custom-rules/build.gradle.kts
@@ -25,9 +25,9 @@ val minSonarQubeApiVersion = "9.14.0.375"
 
 dependencies {
     compileOnly("org.sonarsource.api.plugin:sonar-plugin-api:$minSonarQubeApiVersion")
-    compileOnly("com.felipebz.zpa:sonar-zpa-plugin:3.6.0-SNAPSHOT")
+    compileOnly("com.felipebz.zpa:sonar-zpa-plugin:3.5.1")
     testImplementation("org.sonarsource.sonarqube:sonar-plugin-api-impl:$minSonarQubeVersion")
-    testImplementation("com.felipebz.zpa:zpa-checks-testkit:3.6.0-SNAPSHOT")
+    testImplementation("com.felipebz.zpa:zpa-checks-testkit:3.5.1")
     testImplementation("org.junit.jupiter:junit-jupiter:5.8.0")
 }
 
diff --git a/plsql-custom-rules/pom.xml b/plsql-custom-rules/pom.xml
index 1308e0e7..dc4046cf 100644
--- a/plsql-custom-rules/pom.xml
+++ b/plsql-custom-rules/pom.xml
@@ -10,7 +10,7 @@
   
   <properties>
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-    <zpa.version>3.6.0-SNAPSHOT</zpa.version>
+    <zpa.version>3.5.1</zpa.version>
     <sonarqube.min.version>9.9.0.65466</sonarqube.min.version>
   </properties>
 
diff --git a/template/changelog.tpl b/template/changelog.tpl
index e15e4b2f..241e0870 100644
--- a/template/changelog.tpl
+++ b/template/changelog.tpl
@@ -4,6 +4,19 @@ This release is compatible with SonarQube 9.9 LTA Community Edition and newer. H
 
 Additionally, please note that while this version may work with SonarQube’s commercial editions, the compatibility was not tested and simultaneous analysis using ZPA and SonarSource’s embedded PL/SQL plugin is not supported. If you require this scenario, consider using [zpa-cli](https://github.com/felipebz/zpa-cli) instead.
 
+## Highlights
+
+### First-class support for test and coverage reports generated by utPLSQL
+
+Two new properties specifically designed for consuming test and coverage reports generated by utPLSQL were added:
+
+* `sonar.zpa.tests.reportPaths`: Use this property to specify the path to the test report(s) (generated using the `ut_sonar_test_reporter`).
+* `sonar.zpa.coverage.reportPaths`: Similarly, this property allows you to specify the path to the coverage report(s) (generated using the `ut_coverage_sonar_reporter`).
+
+Previously, importing test and coverage reports into SonarQube required [generic properties](https://docs.sonarsource.com/sonarqube/9.9/analyzing-source-code/test-coverage/generic-test-data/). However, with the introduction of these new properties, the ZPA plugin can now automatically associate the test and coverage results with the corresponding PL/SQL files. The best part? You won’t need to define any complex object-file mapping rules in the utPLSQL-cli.
+
+By leveraging these properties, is much easier to integrate the utPLSQL reports into your SonarQube analysis pipeline. More information is available in the [documentation](https://github.com/felipebz/zpa/wiki/utPLSQL-integration).
+
 ## Install/update instructions
 
 * Download the {{#f_release_download_url}}sonar-zpa-plugin-{{projectVersion}}.jar{{/f_release_download_url}} and copy it to the SONARQUBE_HOME/extensions/plugins.