Prepare release 3.5.2-SNAPSHOT

CHANGELOG.md

@@ -1,7 +1,14 @@
 # Changelog
 
+
+## [3.5.2-SNAPSHOT](https://github.com/jborgers/sonar-pmd/tree/3.5.2-SNAPSHOT) (2024-xx-xx)
+[Full Changelog](https://github.com/jborgers/sonar-pmd/compare/3.5.1..master)
+
+**Implemented highlights:**
+
+
 ## [3.5.1](https://github.com/jborgers/sonar-pmd/tree/3.5.1) (2024-05-07)
-[Full Changelog](https://github.com/jborgers/sonar-pmd/compare/3.5.0...3.5.1)
+[Full Changelog](https://github.com/jborgers/sonar-pmd/compare/3.5.0..3.5.1)
 
 **Implemented highlights:**
 - Supports latest SonarQube [9.9.4 - 10.5+]

RELEASE.md

@@ -7,15 +7,15 @@ Make sure that all commits have been pushed and build
 with `build.yml` workflow before setting and pushing the tag.
 
 Steps:
-- create release notes in `CHANGELOG.md`, update `..master` to `..x.y.z`
-- commit `CHANGELOG.md`
+- create release notes in `CHANGELOG.md`, update `..master` to `..x.y.z`; and update `README.md`
+- commit both
 - `git tag x.y.z`
 - `git push --tags`
 
 The release workflow will be triggered, using the git tag for `-Drevision=<tag>`. 
 
 - manually release staging repo in [Sonatype](https://oss.sonatype.org/#welcome) for Maven Central
-- manually change Github actions release from draft to final here: [releases](https://github.com/jborgers/sonar-pmd/releases)
+- manually change Github actions release from draft to final and limit the changelog here: [releases](https://github.com/jborgers/sonar-pmd/releases) 
 
 Next prepare for next SNAPSHOT:
 

pom.xml

@@ -78,7 +78,7 @@
 
   <properties>
     <!-- use -Drevision=x.y.z to override in build -->
-    <revision>3.5.1-SNAPSHOT</revision>
+    <revision>3.5.2-SNAPSHOT</revision>
     <license.owner>SonarSource SA and others</license.owner>
     <license.mailto>mailto:jborgers AT jpinpoint DOT com; peter.paul.bakker AT stokpop DOT nl</license.mailto>
     <pmd.version>6.55.0</pmd.version>