chore: release v0.1.1#8
Conversation
📝 WalkthroughWalkthroughThe workspace version is bumped from Changesv0.1.1 Release
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8 +/- ##
=======================================
Coverage 58.22% 58.22%
=======================================
Files 31 31
Lines 6344 6344
=======================================
Hits 3694 3694
Misses 2650 2650
Flags with carried forward coverage won't be shown. Click here to find out more. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@crates/codeoid-client/CHANGELOG.md`:
- Around line 10-15: The 0.1.1 section in the CHANGELOG.md file under the
"Other" subsection lacks substantive content describing actual changes in this
patch release. Either add specific features, bug fixes, or improvements that
were included in version 0.1.1 (following the format shown in the codeoid-tui
changelog with clear bullet points), or if there are no user-facing changes,
explicitly document that the release contains only internal dependency updates
or maintenance work. Ensure the changelog entry clearly communicates what users
or developers should know about this release.
In `@crates/codeoid-protocol/CHANGELOG.md`:
- Around line 1-8: The codeoid-protocol CHANGELOG is missing a 0.1.1 release
section that should exist for consistency with codeoid-client and codeoid-tui.
Add a new release section with the version number 0.1.1 after the header
information and before or adjacent to the [Unreleased] section in the changelog
file, following the same format used in the other project changelogs by
including the release date and any relevant PR references or links.
In `@crates/codeoid-tui/CHANGELOG.md`:
- Around line 10-19: The changelog contains a duplicate entry for the
"high-visibility approval banner for pending tool calls ([`#6`])" feature listed
in both the v0.1.1 and v0.1.0 sections. Since this feature originated in v0.1.0,
remove the duplicate entry from the "Added" section under the v0.1.1 release
heading. If v0.1.1 has no other features to list, you can remove the entire
"Added" subsection from v0.1.1, or replace it with the actual features that were
introduced in that release.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 5875e6d4-2f92-43c6-a608-391d6289a820
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock,!**/*.lock
📒 Files selected for processing (4)
Cargo.tomlcrates/codeoid-client/CHANGELOG.mdcrates/codeoid-protocol/CHANGELOG.mdcrates/codeoid-tui/CHANGELOG.md
| ## [0.1.1](https://github.com/saucam/codeoid-ui/compare/codeoid-client-v0.1.0...codeoid-client-v0.1.1) - 2026-06-23 | ||
|
|
||
| ### Other | ||
|
|
||
| - release v0.1.0 ([#7](https://github.com/saucam/codeoid-ui/pull/7)) | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Clarify what's new in codeoid-client 0.1.1.
The 0.1.1 changelog entry only references the prior v0.1.0 release (PR #7) in the "Other" section, with no substantive content describing what changed or improved in 0.1.1. While the PR objectives note API compatibility, the changelog should document what's actually included in this patch release.
Compare this with the codeoid-tui 0.1.1 changelog (lines 12–14 in that file), which clearly lists the "high-visibility approval banner for pending tool calls" feature. If codeoid-client has no user-facing changes, the changelog should at least explain why (e.g., "Internal dependency updates only"). If there are changes, they should be listed.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@crates/codeoid-client/CHANGELOG.md` around lines 10 - 15, The 0.1.1 section
in the CHANGELOG.md file under the "Other" subsection lacks substantive content
describing actual changes in this patch release. Either add specific features,
bug fixes, or improvements that were included in version 0.1.1 (following the
format shown in the codeoid-tui changelog with clear bullet points), or if there
are no user-facing changes, explicitly document that the release contains only
internal dependency updates or maintenance work. Ensure the changelog entry
clearly communicates what users or developers should know about this release.
| # Changelog | ||
|
|
||
| All notable changes to this project will be documented in this file. | ||
|
|
||
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), | ||
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
|
|
||
| ## [Unreleased] |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Add a 0.1.1 release section to codeoid-protocol's CHANGELOG.
The codeoid-protocol changelog is missing a 0.1.1 release entry. Both codeoid-client and codeoid-tui have explicit 0.1.1 sections with release dates and PR references, but codeoid-protocol only contains the header and an [Unreleased] section. For consistency across the workspace, add a matching 0.1.1 release section (even if it documents no user-facing changes, it should state the release date and any relevant links).
🔧 Proposed addition
## [Unreleased]
+## [0.1.1](https://github.com/saucam/codeoid-ui/compare/codeoid-protocol-v0.1.0...codeoid-protocol-v0.1.1) - 2026-06-23
+📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # Changelog | |
| All notable changes to this project will be documented in this file. | |
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), | |
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | |
| ## [Unreleased] | |
| # Changelog | |
| All notable changes to this project will be documented in this file. | |
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), | |
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | |
| ## [Unreleased] | |
| ## [0.1.1](https://github.com/saucam/codeoid-ui/compare/codeoid-protocol-v0.1.0...codeoid-protocol-v0.1.1) - 2026-06-23 | |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@crates/codeoid-protocol/CHANGELOG.md` around lines 1 - 8, The
codeoid-protocol CHANGELOG is missing a 0.1.1 release section that should exist
for consistency with codeoid-client and codeoid-tui. Add a new release section
with the version number 0.1.1 after the header information and before or
adjacent to the [Unreleased] section in the changelog file, following the same
format used in the other project changelogs by including the release date and
any relevant PR references or links.
| ## [0.1.1](https://github.com/saucam/codeoid-ui/compare/v0.1.0...v0.1.1) - 2026-06-23 | ||
|
|
||
| ### Added | ||
|
|
||
| - high-visibility approval banner for pending tool calls ([#6](https://github.com/saucam/codeoid-ui/pull/6)) | ||
|
|
||
| ### Other | ||
|
|
||
| - release v0.1.0 ([#7](https://github.com/saucam/codeoid-ui/pull/7)) | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔴 Critical | ⚡ Quick win
Remove duplicate feature entry from 0.1.1 section.
The "high-visibility approval banner for pending tool calls ([#6])" appears twice in this changelog:
- Line 14 (in the 0.1.1 Added section)
- Line 24 (in the 0.1.0 Added section)
A feature cannot be introduced in both v0.1.0 and v0.1.1. The approval banner originated in v0.1.0 (PR #6), so it should only appear in the v0.1.0 section. Remove it from the 0.1.1 "Added" section.
This appears to be a copy-paste error during changelog generation.
🐛 Proposed fix to remove the duplicate entry
## [0.1.1](https://github.com/saucam/codeoid-ui/compare/v0.1.0...v0.1.1) - 2026-06-23
-### Added
-
-- high-visibility approval banner for pending tool calls ([`#6`](https://github.com/saucam/codeoid-ui/pull/6))
-
### Other
- release v0.1.0 ([`#7`](https://github.com/saucam/codeoid-ui/pull/7))Alternative: If the 0.1.1 release does have new features, replace the approval banner entry with those features instead of removing the "Added" section entirely.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@crates/codeoid-tui/CHANGELOG.md` around lines 10 - 19, The changelog contains
a duplicate entry for the "high-visibility approval banner for pending tool
calls ([`#6`])" feature listed in both the v0.1.1 and v0.1.0 sections. Since this
feature originated in v0.1.0, remove the duplicate entry from the "Added"
section under the v0.1.1 release heading. If v0.1.1 has no other features to
list, you can remove the entire "Added" subsection from v0.1.1, or replace it
with the actual features that were introduced in that release.
saucam
force-pushed
the
release-plz-2026-06-23T16-59-11Z
branch
2 times, most recently
from
314f9d8 to
5ad57e8
Compare
saucam
force-pushed
the
release-plz-2026-06-23T16-59-11Z
branch
from
5ad57e8 to
006adce
Compare
1 participant
🤖 New release
codeoid-protocol: 0.1.0 -> 0.1.1codeoid-client: 0.1.0 -> 0.1.1 (✓ API compatible changes)codeoid-tui: 0.1.0 -> 0.1.1Changelog
codeoid-clientcodeoid-tuiThis PR was generated with release-plz.