release: aegis 0.7.5 - #697
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (3)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe PR updates release documentation, adds a ChangesIntegration wiring updates
Release documentation updates
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 markdownlint-cli2 (0.22.1)DEVELOP.mdmarkdownlint-cli2 v0.22.1 (markdownlint v0.40.0) docs/CHANGELOG.mdmarkdownlint-cli2 v0.22.1 (markdownlint v0.40.0) Comment |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- In
default_llm_model, switching fromGoogleProvider(**provider_kwargs)to onlyGoogleProvider(http_client=provider_kwargs["http_client"])may drop other configuration options previously passed viaprovider_kwargs; consider either preserving the full set of kwargs or making the set of supported parameters explicit so behavior remains consistent. - The MCP tooling variables are still named
*_stdio_servereven though they now holdMCPToolsetinstances; consider renaming these to reflect the new abstraction to avoid confusion for future readers.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In `default_llm_model`, switching from `GoogleProvider(**provider_kwargs)` to only `GoogleProvider(http_client=provider_kwargs["http_client"])` may drop other configuration options previously passed via `provider_kwargs`; consider either preserving the full set of kwargs or making the set of supported parameters explicit so behavior remains consistent.
- The MCP tooling variables are still named `*_stdio_server` even though they now hold `MCPToolset` instances; consider renaming these to reflect the new abstraction to avoid confusion for future readers.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@src/aegis_ai/toolsets/__init__.py`:
- Line 98: The GitHub MCP server image reference is unpinned and should be
updated to a reviewed immutable version. In the toolset definition in
__init__.py, replace the bare ghcr.io/github/github-mcp-server image string with
a specific release tag or digest in the same place it is added to the server
list so the runtime uses a fixed version.
- Around line 90-99: The GitHub MCP Podman invocation currently leaves exited
containers behind after each run; update the container launch in the GitHub MCP
setup (the Podman command array in the toolset initialization) to include
automatic cleanup. Add the missing --rm flag to the podman run arguments so
repeated sessions don’t accumulate stale containers.
🪄 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: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: 93aefa48-f968-492d-9543-e230ff474ad1
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (4)
DEVELOP.mddocs/CHANGELOG.mdsrc/aegis_ai/__init__.pysrc/aegis_ai/toolsets/__init__.py
... so that we use supported versions of the modules we depend on.
Migrate MCP servers from deprecated `MCPServerStdio` to `MCPToolset` + `StdioTransport`, using `.prefixed()` for tool prefixes. Fix `GoogleProvider` overload mismatch by passing `http_client` explicitly instead of via `**provider_kwargs`. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ontainers Suggested-By: https://github.com/apps/coderabbitai Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@src/aegis_ai/toolsets/__init__.py`:
- Around line 67-75: The NVD MCP toolset setup in MCPToolset/StdioTransport does
not forward the parent environment, so the spawned mcp-nvd process cannot read
NVD_API_KEY. Update the nvd_mcp_toolset construction to explicitly pass
NVD_API_KEY into the StdioTransport environment for the mcp-nvd subprocess,
while keeping the existing .prefixed("mitre_nvd") setup intact.
🪄 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: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: caacbe4d-5bb7-4348-a755-8ae06413325e
📒 Files selected for processing (4)
DEVELOP.mddocs/CHANGELOG.mdsrc/aegis_ai/__init__.pysrc/aegis_ai/toolsets/__init__.py
✅ Files skipped from review due to trivial changes (3)
- src/aegis_ai/init.py
- DEVELOP.md
- docs/CHANGELOG.md
2 participants
What
Prepare the 0.7.5 release: update pinned dependencies, fix type errors from pydantic-ai v2, update the changelog, and streamline the release checklist.
Why
The pydantic-ai v2 upgrade deprecated
MCPServerStdioand changedGoogleProvideroverloads, breakingtytype checks. The release checklist inDEVELOP.mdstill referenced manual PyPI publishing steps that are now automated.How to Test
Related Tickets
Summary by Sourcery
Prepare the 0.7.5 release by updating MCP integrations for pydantic-ai v2, adjusting Google provider initialization, refreshing release docs, and syncing dependencies and changelog.
Enhancements:
Build:
Documentation: