rel: prep v0.2.4b0 (#169)

## Which problem is this PR solving?

new release with latest otel versions

## Short description of the changes

- update version to 0.2.4b0
- update changelog for 0.2.4b0
- update readme with new otel version
- update releasing doc for consistency

Author: JamieDanielson

CHANGELOG.md

@@ -1,5 +1,15 @@
 # honeycomb-opentelemetry-python changelog
 
+## [0.2.4b0] - 2024-01-18
+
+### Maintenance
+
+- maint(deps-dev): bump pylint from 2.17.6 to 2.17.7 (#162) | dependabot[bot]
+- maint(deps-dev): bump the testing-dependencies group with 1 update (#163) | dependabot[bot]
+- maint(deps): update otel to 1.22 and 0.43b0 (#168) | @JamieDanielson
+- maint: update codeowners to pipeline-team (#166) | @JamieDanielson
+- maint: update codeowners to pipeline (#165) | @JamieDanielson
+
 ## [0.2.3b0] - 2023-09-25
 
 ### Fixes

README.md

@@ -12,7 +12,7 @@ It makes getting started with OpenTelemetry and Honeycomb easier!
 
 Latest release built with:
 
-- [OpenTelemetry version 1.19.0/0.40b0](https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.19.0)
+- [OpenTelemetry version 1.22.0/0.43b0](https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.22.0)
 
 ## Requirements
 

RELEASING.md

@@ -8,12 +8,14 @@
 ```
 
 - Confirm the version number update appears in `src/pyproject.toml`.
-- Update `CHANGELOG.md` with the changes since the last release.
-- If this release bumps OTel versions, update `README.md`.
+- 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'`
+- If the upstream OpenTelemetry package versions have changed, update `README.md` with new versions and links.
 - 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`
-- Copy change log entry for newest version into draft GitHub release created as part of CI publish steps.
-  - Make sure to "generate release notes" in github for full changelog notes and any new contributors
-- Publish the github draft release and this will kick off publishing to GitHub and the PyPI registry.
+- Ensure that there is a draft GitHub release created as part of CI publish steps (this will also publish to PyPI).
+- Click "generate release notes" in GitHub for full changelog notes and any new contributors
+- Publish the github draft release - if it is a prerelease (e.g., beta) click the prerelease checkbox.

pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "honeycomb-opentelemetry"
-version = "0.2.3b0"
+version = "0.2.4b0"
 description = "Honeycomb OpenTelemetry Distro for Python"
 authors = ["Honeycomb <[email protected]>"]
 readme = "README.md"