Update changelog for CLI v0.0.179

[devin-ai-integration]

Update changelog for CLI v0.0.179

Summary

Updates the CHANGELOG.md to document the changes in CLI version v0.0.179 released on October 23, 2025. This release includes two changes:

• A dependency update (go-common bumped to 1.0.111)
• A bug fix (corrected eval API endpoint from /cli/evals to /cli/eval)

Also adds version comparison links for v0.0.179, v0.0.178, and v0.0.177 at the bottom of the changelog following the existing pattern.

Review & Testing Checklist for Human

• Verify completeness: Confirm that PRs bump to go-common 1.0.111 #475 and Updated eval endpoint #477 are the only changes between v0.0.178 and v0.0.179. You can check with git log v0.0.178..v0.0.179 --oneline to verify no PRs were missed.
• Verify categorization: Confirm that PR bump to go-common 1.0.111 #475 is correctly categorized as "Changed" and PR Updated eval endpoint #477 as "Fixed" based on the nature of the changes.
• Check version links: Note that v0.0.177 and v0.0.178 don't have changelog entries but do have comparison links added. Verify this is intentional or if those versions need entries.

Notes

• This is a documentation-only change following the Keep a Changelog format
• The release date (October 23, 2025) was extracted from the git tag timestamp
• A corresponding PR will be created for the docs repository to update the CLI changelog page there as well

Link to Devin run: https://app.devin.ai/sessions/2f01940b2b6d4d6d866c69fd64a1a123
Requested by: unknown ()

Summary by CodeRabbit

• Changed

  • Updated go-common dependency to version 1.0.111

• Bug Fixes

  • Corrected the API endpoint used for creating evals

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[coderabbitai]

Walkthrough

The pull request updates CHANGELOG.md with a new release entry v0.0.179 dated 2025-10-23, documenting a dependency bump to go-common 1.0.111 and an API endpoint correction for creating evals.

Changes

Cohort / File(s)	Change Summary
Release Documentation CHANGELOG.md	Added v0.0.179 release entry with dependency bump and API endpoint fix; included release anchors for v0.0.179, v0.0.178, and v0.0.177

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• jhaynie

Poem

🐰 A version hops forward with fixes so neat,
Endpoints corrected, dependencies complete!
v0.0.179 bounces with care,
Changes logged gently through autumn's cool air. 🌙

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Update changelog for CLI v0.0.179" clearly and directly summarizes the main purpose of this pull request. It accurately describes what the changeset does—updating the CHANGELOG.md file to document the v0.0.179 release with its associated changes (dependency bump and API endpoint fix). The title is concise, specific, and non-vague, providing sufficient clarity for a teammate scanning the commit history to understand the PR's primary objective at a glance.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch devin/1761236647-update-changelog-v0.0.179

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 97546d1 and 5e561d0.

📒 Files selected for processing (1)

• CHANGELOG.md (2 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

CHANGELOG.md

927-927: Link and image reference definitions should be needed
Unused link or image reference definition: "v0.0.178"

(MD053, link-image-reference-definitions)

---

928-928: Link and image reference definitions should be needed
Unused link or image reference definition: "v0.0.177"

(MD053, link-image-reference-definitions)

🔇 Additional comments (2)

CHANGELOG.md (2)

8-15: ✓ v0.0.179 changelog entry looks good.

The new release section follows Keep a Changelog format correctly, with proper categorization of changes: go-common dependency bump (Changed) and API endpoint correction (Fixed). Both PRs are correctly linked.

---

926-928: Note: Markdownlint flags unused reference definitions for v0.0.178 and v0.0.177.

The static analysis tool reports that the reference link definitions on lines 927–928 are unused because no changelog entries exist for those versions. Per the PR objectives, this appears intentional—adding comparison links for versions without entries. However, verify this aligns with your project's standards for handling skipped/unreleased versions in the changelog.

If you'd like to suppress the linter warnings, add a <!-- markdownlint-disable MD053 --> comment around those lines, or confirm with your team that this pattern is acceptable.

---

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