chore(main): release 0.2.23

[mateodelnorte]

🤖 I have created a release beep boop

0.2.23 (2026-08-02)

Features

• org rename (#94) (a44337c)

Bug Fixes

• hooks: isolate Git-local test environment (#98) (ae5818b)
• remove agent plugins (#96) (4d8adcc)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 42 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: cfdbb1a4-f863-4999-b534-06f8716b9824

📥 Commits

Reviewing files that changed from the base of the PR and between 8e1421e and 911876b.

📒 Files selected for processing (4)

• .release-please-manifest.json
• CHANGELOG.md
• Cargo.toml
• VERSION

Walkthrough

This PR bumps the project version from 0.2.22 to 0.2.23 across the release manifest, Cargo.toml, and VERSION file, and adds a corresponding CHANGELOG.md entry documenting an "org rename" feature.

Changes

Release version bump

Layer / File(s)	Summary
Version bump and changelog entry Cargo.toml, VERSION, .release-please-manifest.json, CHANGELOG.md	Updates version strings from 0.2.22 to 0.2.23 in Cargo.toml, VERSION, and the release manifest, and adds a new CHANGELOG.md entry for 0.2.23 documenting an "org rename" feature.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

Four little files, one number to raise,
0.2.23 hops through the maze 🐇
Manifest, toml, VERSION in tow,
CHANGELOG whispers where the org renames go.
A tiny bump, a joyful cheer—
onward we hop into the next frontier!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies this pull request as the 0.2.23 release on the main branch.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main

---

_{Comment @coderabbitai help to get the list of available commands.}