rel: prep release 2.3.0 (#321)

## Which problem is this PR solving?

- new release

## Short description of the changes

- update releasing doc
- update version (and remove redundant version; example app will use
parent version bc it's a module)
- update changelog

CHANGELOG.md

@@ -1,5 +1,23 @@
 # Beeline Changelog
 
+## [2.3.0] - 2025-01-17
+
+### Fixes
+
+- fix: set service name in spring boot starter (#317) | @JamieDanielson
+
+**NOTE**: this is technically a **breaking change** for Spring applications instrumented with Beeline.
+
+- If using a **Classic** key, and the `service.name` attribute was previously left empty and relied on `spring.application.name`, it will now have `unknown_service:java` for that attribute but will continue to send to the configured dataset. Set `honeycomb.beeline.dataset` for dataset in Honeycomb.
+- If using an **Environments & Services** key, data will be sent to the configured `service.name` attribute; if that is not set, it will be sent to `unknown_service:java` in Honeycomb. Set `honeycomb.beeline.service-name` for dataset in Honeycomb.
+
+### Maintenance
+
+- maint(deps): bump org.apache.maven.plugins:maven-javadoc-plugin from 3.4.1 to 3.11.2 (#319) | dependabot[bot]
+- maint(deps): bump net.bytebuddy:byte-buddy from 1.14.3 to 1.15.11 (#318) | dependabot[bot]
+- maint: remove and gitignore bin (#316) | @JamieDanielson
+- maint: Update README.md (#314) | @codeboten
+
 ## [2.2.0] - 2024-03-07
 
 ### Enhancements

RELEASING.md

@@ -1,7 +1,13 @@
 # Creating a new release
 
-1. Update the `<version>` tag in each pom.xml in the repo.
-2. Add new release notes to the Changelog.
-3. Open a PR with those changes.
-4. Once the above PR is merged, tag `main` with the new version, e.g. `v0.1.1`. Push the tags. This will kick off a CI workflow, which will publish a draft GitHub release, and publish artifacts to Maven.
-5. Update Release Notes on the new draft GitHub release, and publish that.
+- Update the `<version>` tag in each pom.xml in the repo.
+- Update `CHANGELOG.md` with the changes since the last release. Consider automating with a command such as these two:
+  - `git log $(git describe --tags --abbrev=0)..HEAD --no-merges --oneline > new-in-this-release.log`
+  - `git log --pretty='%C(green)%d%Creset- %s | [%an](https://github.com/)'`
+- Commit changes, push, and open a release preparation pull request for review.
+- Once the pull request is merged, fetch the updated `main` branch.
+- Apply a tag for the new version on the merged commit (e.g. `git tag -a v2.3.1 -m "v2.3.1"`).
+- Push the tag upstream (this will kick off the release pipeline in CI) e.g. `git push origin v2.3.1`.
+- Ensure that there is a draft GitHub release created as part of CI publish steps (this will also publish to Maven).
+- Click "generate release notes" in GitHub for full changelog notes and any new contributors.
+- Publish the GitHub draft release.

beeline-core/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.honeycomb.beeline</groupId>
         <artifactId>beeline-parent</artifactId>
-        <version>2.2.0</version>
+        <version>2.3.0</version>
     </parent>
 
     <name>Beeline Java (Core)</name>

beeline-spring-boot-sleuth-starter/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.honeycomb.beeline</groupId>
         <artifactId>beeline-parent</artifactId>
-        <version>2.2.0</version>
+        <version>2.3.0</version>
     </parent>
 
     <name>Beeline Java (Spring Boot Sleuth Starter)</name>

beeline-spring-boot-starter/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>io.honeycomb.beeline</groupId>
         <artifactId>beeline-parent</artifactId>
-        <version>2.2.0</version>
+        <version>2.3.0</version>
     </parent>
 
     <name>Beeline Java (Spring Boot Starter)</name>

example-spring/pom.xml

@@ -6,12 +6,10 @@
     <parent>
           <groupId>io.honeycomb.beeline</groupId>
           <artifactId>beeline-parent</artifactId>
-          <version>2.2.0</version>
+          <version>2.3.0</version>
     </parent>
 
-    <groupId>io.honeycomb.beeline</groupId>
     <artifactId>example-spring</artifactId>
-    <version>2.2.0</version>
 
     <properties>
         <maven.compiler.source>17</maven.compiler.source>

examples/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <artifactId>beeline-parent</artifactId>
         <groupId>io.honeycomb.beeline</groupId>
-        <version>2.2.0</version>
+        <version>2.3.0</version>
     </parent>
 
     <artifactId>examples</artifactId>

pom.xml

@@ -7,7 +7,7 @@
     <name>Beeline Java (Parent)</name>
     <artifactId>beeline-parent</artifactId>
     <groupId>io.honeycomb.beeline</groupId>
-    <version>2.2.0</version>
+    <version>2.3.0</version>
     <packaging>pom</packaging>
 
     <description>Parent POM for the Honeycomb Beeline for Java</description>