Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions content/Changelog/cli.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,16 +6,24 @@ description: Release notes and version history for the Agentuity CLI
import { Callout } from 'fumadocs-ui/components/callout';

This page documents the release history of the [Agentuity CLI](https://github.com/agentuity/cli).
## v0.0.175

## v0.0.178

<Callout type="info">
Released: October 13, 2025
Released: October 22, 2025
</Callout>

**Changes:**
- **Changed**: Bump go-common to remove gravity log ([#466](https://github.com/agentuity/cli/pull/466))
- **Added**: Add eval support ([#472](https://github.com/agentuity/cli/pull/472))

## v0.0.177

<Callout type="info">
Released: October 22, 2025
</Callout>

**Changes:**
- No changes documented
Comment on lines +10 to +26
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

New version entries are properly formatted; verify release metadata and scope.

The v0.0.178 and v0.0.177 entries follow the correct structure with release dates and change descriptions. However, confirm that:

  • v0.0.177 release tag exists and actually had no changes (as marked)
  • v0.0.178 only contains PR #472 and no other merged PRs between the two releases

[/request_verification]


🏁 Script executed:

#!/bin/bash
# Verify v0.0.177 and v0.0.178 release tags and commits between them
cd /tmp && git clone https://github.com/agentuity/cli.git --quiet 2>/dev/null
cd cli

# Check if both tags exist
echo "=== Checking if release tags exist ==="
git tag | grep -E "v0.0.17[78]" || echo "Tag not found"

# Show commits between v0.0.177 and v0.0.178
echo -e "\n=== Commits between v0.0.177 and v0.0.178 ==="
git log v0.0.177..v0.0.178 --oneline 2>/dev/null | head -20 || echo "Cannot list commits; tags may not exist"

# Verify v0.0.177 was released (check if tag exists with no additional commits after v0.0.176)
echo -e "\n=== Tag information for v0.0.177 ==="
git show v0.0.177 --quiet 2>/dev/null | head -10 || echo "v0.0.177 tag details unavailable"

Length of output: 481


[/run_scripts]


🏁 Script executed:

#!/bin/bash
# Verify line 457 duplicate text and duplicate version entries
cat content/Changelog/cli.mdx | sed -n '455,460p'
echo -e "\n=== Checking for duplicate version entries around lines 500-641 ==="
# Search for version patterns that appear multiple times
grep -n "^## v0.0.1[0-9][0-9]" content/Changelog/cli.mdx | tail -40

Length of output: 955


Remove stray line 457 text, fix duplicate version entries, and clarify v0.0.177 changes.

Three critical issues found:

  1. Line 457 stray text: "This page documents the release history..." appears mid-changelog between version entries and breaks document flow. Remove this line.

  2. Duplicate version entries: v0.0.124 through v0.0.129 (and possibly v0.0.130–v0.0.131) appear twice in the file (first set around lines 500–545, second set around lines 559–622). Remove the duplicate entries.

  3. v0.0.177 documentation mismatch: Git tag shows message "dedicated url" (Oct 20, 2025), but changelog entry states "No changes documented." Either document the actual change or verify that the tag message is unrelated to release content and update accordingly.

🤖 Prompt for AI Agents
In content/Changelog/cli.mdx around lines 10–26 and the rest of the file
(notably line ~457 and the sections around ~500–622), remove the stray mid-file
sentence "This page documents the release history..." at line ~457; find and
delete the duplicate version blocks for v0.0.124 through v0.0.129 (and duplicate
v0.0.130–v0.0.131 if present) so each version appears only once; and update the
v0.0.177 entry to reflect the git tag message "dedicated url" by either adding a
short change bullet describing that change (e.g., “Updated dedicated URL
handling”) or, if the tag is unrelated, replace "No changes documented" with a
clarifying note like "Tag message: 'dedicated url' — no release changes
recorded" after verifying with the author.


## v0.0.176

Expand Down