release process (#811)

* release process

* release process

.github/renovate.json5

@@ -41,6 +41,12 @@
         "update-digest"
       ],
     },
+    {
+      // is only used for running "markdownlint -f ." locally
+      matchFileNames: [ ".tool-versions" ],
+      matchPackageNames: [ "nodejs"],
+      enabled: false
+    },
     {
       // keep spring 2 examples
       "matchFileNames": [

.tool-versions

@@ -1,2 +1,2 @@
 java temurin-21.0.5+11.0.LTS
-nodejs 22.11.0
+nodejs 19.8.1

RELEASING.md

@@ -5,5 +5,11 @@
    (run workflow)
 2. Go to <https://github.com/grafana/grafana-opentelemetry-java/releases>
 3. Click on "Choose a tag", enter the tag name (e.g. `v0.1.0`), and click "Create a new tag".
+   The version number should be the same as the
+   [upstream version](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases) that we are using.
+   Bugfix releases should be `v2.3.4.1`, where `2.3.4` is the upstream version.
 4. Click on "Generate release notes" to auto-generate the release notes based on the commits since the last release.
+   - Exclude the commits that are not relevant for the release notes, such as "Update dependencies".
+   - Usually, it's just updating the upstream version.
+   - Include a link to the upstream release notes, e.g. "Update to [OpenTelemetry 2.9.0](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md#version-290-2024-10-17)".
 5. Click on "Publish release".

build.gradle

@@ -1,5 +1,5 @@
 group 'com.grafana'
-version '2.9.0'
+version '10.0.0-SNAPSHOT' // the version of the actual release is set during the release process in build-release.sh
 
 buildscript {
   ext {

custom/src/main/java/com/grafana/extensions/resources/internal/DistributionVersion.java

@@ -9,5 +9,5 @@
 
 public class DistributionVersion {
 
-  public static final String VERSION = "2.9.0";
+  public static final String VERSION = "10.0.0-SNAPSHOT";
 }