Bump version from 0.2.2 to 0.2.3

[torlando-tech]

No description provided.

[greptile-apps]

Confidence Score: 4/5

[Low risk] Version number bump in package metadata.

Do not merge this as the complete 0.2.3 release bump; the release job will reject the tag without its changelog entry.

Findings

1.  The release cannot publish ▶

Fix with agent prompt

### Issue 1
pyproject.toml:7
When a maintainer tags `v0.2.3`, the release job requires a non-empty `0.2.3` section in `CHANGELOG.md`. This version bump adds no such section, so the job stops before publishing. Add the release notes alongside the version bump.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The ble-reticulum project metadata now declares version 0.2.3 instead of 0.2.2.

• The package name and other project settings are unchanged.

_{Reviews (1) · Last reviewed commit: "Bump version from 0.2.2 to 0.2.3"}

[greptile-apps]

The release cannot publish

When a maintainer tags v0.2.3, the release job requires a non-empty 0.2.3 section in CHANGELOG.md. This version bump adds no such section, so the job stops before publishing. Add the release notes alongside the version bump.

Knowledge Base Used: Release and automation workflows

Prompt To Fix With AI

This is a comment left during a code review.
Path: pyproject.toml
Line: 7

Comment:
**The release cannot publish**

When a maintainer tags `v0.2.3`, the release job requires a non-empty `0.2.3` section in `CHANGELOG.md`. This version bump adds no such section, so the job stops before publishing. Add the release notes alongside the version bump.

**Knowledge Base Used:** [Release and automation workflows](https://app.greptile.com/torlando-tech/-/custom-context/knowledge-base/torlando-tech/ble-reticulum/-/docs/release-and-automation-workflows.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.