Skip to content
Merged
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.2.0
0.2.1
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion | 🟠 Major

🧩 Analysis chain

Verify version consistency and changelog updates across the project.

The VERSION file has been updated to 0.2.1, but several cross-cutting concerns need verification:

  1. Version consistency: Is this version updated in all project files (e.g., setup.py, package.json, pyproject.toml, init.py)?
  2. Release documentation: Has a CHANGELOG been updated to document what fixes/features are included in this patch release?
  3. PR context: The PR description is empty. For version bumps, it's important to document the motivation and related issues/PRs to maintain clear audit trails.

Run the following script to verify version references across the project:


🏁 Script executed:

#!/bin/bash
# Description: Search for version references to ensure consistency across the project.

echo "=== Checking version references ==="
rg -n "0\.2\.(0|1)" --type=py --type=toml --type=json --type=yaml --type=txt -g '!.git' | head -20

echo ""
echo "=== Checking for CHANGELOG files ==="
fd -i changelog -o fd -i 'release.*notes' | head -10

echo ""
echo "=== Checking setup.py or pyproject.toml for version strings ==="
fd -e py -e toml | xargs -I {} grep -l "version" {} 2>/dev/null | head -10

Length of output: 1715


🏁 Script executed:

#!/bin/bash
# Description: Inspect actual version definitions across project files

echo "=== Checking pyproject.toml [project] section ==="
grep -A5 "^\[project\]" pyproject.toml | head -10

echo ""
echo "=== Checking rogue/__init__.py for __version__ ==="
head -20 rogue/__init__.py

echo ""
echo "=== Checking rogue/common/version.py ==="
cat rogue/common/version.py 2>/dev/null || echo "File not found"

echo ""
echo "=== Finding CHANGELOG/HISTORY/RELEASE files ==="
find . -maxdepth 2 -type f \( -iname "CHANGELOG*" -o -iname "HISTORY*" -o -iname "RELEASE*" -o -iname "NEWS*" \) 2>/dev/null

echo ""
echo "=== Checking if version 0.2.1 appears anywhere in those discovered files ==="
grep -r "0\.2\.1" . --include="CHANGELOG*" --include="HISTORY*" --include="RELEASE*" --include="NEWS*" 2>/dev/null || echo "No matches in changelog/history/release files"

Length of output: 2010


Create a CHANGELOG documenting the 0.2.1 release and provide context in PR description.

Version 0.2.1 in the VERSION file is properly structured for the project (it's read by rogue/common/version.py's get_version() function and pyproject.toml correctly uses dynamic = ["version"]). However:

  1. No CHANGELOG exists in the project. Version 0.2.1 has no documentation of what fixes, features, or changes prompted this patch-level bump.
  2. Empty PR description provides no context. For maintainability and audit trails, the PR should document:
    • What motivated the patch bump (bug fixes, features, etc.)?
    • Which issues or prior PRs does this resolve?
    • Any breaking changes or migration notes?

Add a CHANGELOG.md file documenting the 0.2.1 release, and fill out the PR description with context.

🤖 Prompt for AI Agents
In VERSION around line 1, the repo was bumped to 0.2.1 but there is no CHANGELOG
or PR context; create a new CHANGELOG.md at the repo root documenting the 0.2.1
release (release heading with date and version), list the
fixes/features/bugfixes included in this patch, reference related issue and PR
numbers, note any breaking changes or migration steps (if none, state "no
breaking changes"), and add a concise PR description that states why the bump
was made, what it fixes, which issues/PRs it closes, and any developer/user
impact.

5 changes: 2 additions & 3 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ dependencies = [
"backoff>=2.2.1",
"click>=8.0.0",
"datasets==3.6.0",
"fastapi>=0.115.0",
"fastapi>=0.121.0",
"fastmcp>=2.12.5",
"google-adk==1.5.0",
"gradio==5.35.0",
Expand All @@ -24,7 +24,7 @@ dependencies = [
"requests>=2.32.4",
"rich>=14.0.0",
"rogue-ai-sdk>=0.1.3",
"uvicorn>=0.32.0",
"uvicorn>=0.38.0",
]

[dependency-groups]
Expand Down Expand Up @@ -70,4 +70,3 @@ rogue-ai-sdk = { path = "sdks/python", editable = true }
[project.scripts]
rogue-ai = "rogue.__main__:main"
rogue-ai-example-tshirt = "examples.tshirt_store_agent.__main__:main"

13 changes: 13 additions & 0 deletions rogue/__main__.py
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
import subprocess # nosec: B404
import sys
import time
import warnings
from argparse import ArgumentParser, Namespace
from pathlib import Path

Expand All @@ -18,6 +19,18 @@
from .run_tui import run_rogue_tui
from .run_ui import run_ui, set_ui_args

# Suppress the specific Uvicorn/websockets deprecation warnings
warnings.filterwarnings(
"ignore",
category=DeprecationWarning,
message="websockets.legacy is deprecated",
)
warnings.filterwarnings(
"ignore",
category=DeprecationWarning,
message="websockets.server.WebSocketServerProtocol is deprecated",
)

load_dotenv()


Expand Down
26 changes: 18 additions & 8 deletions uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading