-
Notifications
You must be signed in to change notification settings - Fork 7
Update changelog for v0.0.178 #476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-Authored-By: unknown <>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
WalkthroughTwo new release entries were added to the changelog. Version 0.0.178 documents the addition of eval support linked to PR #472. Version 0.0.177 was added with a note indicating no changes were documented for that release. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
CHANGELOG.md (1)
13-16: Remove the "Changed" section from v0.0.177 or leave the entry empty.Per Keep a Changelog best practices, empty sections should be removed as they occupy space and create noise; people will assume missing sections were intentionally omitted because they contained no notable changes. Line 15-16 uses a "Changed" section with "No changes documented", which is semantically incorrect and violates the format convention.
Suggested fix: Remove lines 15-16 entirely, leaving only the version header and date:
## [v0.0.177] - 2025-10-22 - -### Changed -- No changes documentedAlternatively, if you want to explicitly document that a release exists but has no changes, consider adding a comment above the version entry (outside the changelog sections) rather than using a formal changelog section.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
CHANGELOG.md(1 hunks)
🔇 Additional comments (1)
CHANGELOG.md (1)
8-11: Add version links for v0.0.178 at the end of the file.The new v0.0.178 entry is properly formatted, but the corresponding version link is missing from the reference section at the bottom of the file. All other versions have links in the format
[v0.0.XXX]: https://github.com/agentuity/cli/compare/.... Add a similar link for v0.0.178 comparing against v0.0.177.
|
Closing due to inactivity for more than 30 days. Configure here. |
Update changelog for v0.0.178
Summary
This PR updates the CHANGELOG.md file to document releases v0.0.178 and v0.0.177 following the Keep a Changelog format.
Changes:
Review & Testing Checklist for Human
Notes
Summary by CodeRabbit
New Features
Documentation