Conversation
WalkthroughThe changes update the pinned version of the Changes
Sequence Diagram(s)sequenceDiagram
participant Developer
participant Dockerfile
participant Pip
participant PraisonAI
Developer->>Dockerfile: Build image
Dockerfile->>Pip: Install praisonai==2.2.0
Pip->>PraisonAI: Download and install package
PraisonAI-->>Dockerfile: Available in container
Poem
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure ✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @MervinPraison, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
Hello team, Gemini here with a summary of this pull request. This PR, titled "v2.2 with MCP SSE and STDIO", primarily focuses on updating the project's core dependencies to their latest versions, specifically praisonai to 2.2.0 and praisonaiagents to 0.0.83. It also adjusts the dependency constraint for mcp to allow versions greater than or equal to 1.6.0. The changes are reflected across various Dockerfiles, documentation files, pyproject.toml, and the uv.lock file to ensure consistency and leverage the new features or fixes in the updated packages. The update to praisonaiagents also includes adding fastapi and uvicorn as dependencies for the mcp extra, likely related to the "MCP SSE and STDIO" mentioned in the title, potentially enabling new real-time communication or deployment options.
Highlights
- Version Updates: The main
praisonaipackage is updated from version2.1.6to2.2.0. - Dependency Updates: The
praisonaiagentsdependency is updated from>=0.0.82to>=0.0.83. Themcpdependency constraint is changed from==1.6.0to>=1.6.0. - New MCP Dependencies: The
mcpoptional dependency group withinpraisonaiagentsnow includesfastapianduvicorn. - Configuration and Documentation Sync: Dockerfiles, documentation examples,
pyproject.toml, anduv.lockhave all been updated to reflect the new package versions and dependency constraints.
Changelog
Click here to see the changelog
- docker/Dockerfile
- Updated
praisonaiversion from2.1.6to2.2.0on line 4.
- Updated
- docker/Dockerfile.chat
- Updated
praisonaiversion from2.1.6to2.2.0on line 16.
- Updated
- docker/Dockerfile.dev
- Updated
praisonaiversion from2.1.6to2.2.0on line 18.
- Updated
- docker/Dockerfile.ui
- Updated
praisonaiversion from2.1.6to2.2.0on line 16.
- Updated
- docs/api/praisonai/deploy.html
- Updated
praisonaiversion in the Dockerfile example from2.1.6to2.2.0on line 113.
- Updated
- docs/developers/local-development.mdx
- Updated
praisonaiversion in the Dockerfile example from2.1.6to2.2.0on line 30.
- Updated
- docs/ui/chat.mdx
- Updated
praisonaiversion in the Dockerfile example from2.1.6to2.2.0on line 158.
- Updated
- docs/ui/code.mdx
- Updated
praisonaiversion in the Dockerfile example from2.1.6to2.2.0on line 211.
- Updated
- praisonai/deploy.py
- Updated the hardcoded
praisonaiversion used when generating a Dockerfile from2.1.6to2.2.0on line 59.
- Updated the hardcoded
- pyproject.toml
- Updated
praisonaiproject version from2.1.6to2.2.0on line 3. - Updated
praisonaiagentsdependency constraint from>=0.0.82to>=0.0.83on line 15. - Updated
mcpdependency constraint from==1.6.0to>=1.6.0on line 19. - Updated
tool.poetrysection withpraisonaiversion2.2.0on line 92. - Updated
tool.poetry.dependencieswithpraisonaiagents>=0.0.83andmcp>=1.6.0on lines 110 and 114.
- Updated
- src/praisonai-agents/pyproject.toml
- Updated
praisonaiagentsproject version from0.0.82to0.0.83on line 7. - Added
fastapianduvicornto themcpoptional dependency group on lines 22 and 23.
- Updated
- uv.lock
- Updated
praisonaiversion from2.1.6to2.2.0on line 3617. - Updated
praisonaiagentsversion from0.0.82to0.0.83and updated its sdist/wheel URLs and hashes on lines 3759 and 3816. - Updated
mcpdependency specifier from==1.6.0to>=1.6.0on line 3752.
- Updated
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Dependencies align,
New versions ship in time,
Code's future is bright.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
✅ Deploy Preview for praisonai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Code Review
This pull request updates the project to version 2.2.0, incorporating changes related to MCP SSE and STDIO support. The core changes involve updating package versions and adding necessary dependencies for the new features. The documentation and deployment scripts have been updated accordingly. Overall, the changes appear straightforward and aligned with the stated objective.
Summary of Findings
- Version Updates: The pull request consistently updates the
praisonaiandpraisonaiagentspackage versions across the Dockerfiles,pyproject.toml, anduv.lockfiles. The documentation files have also been updated to reflect the newpraisonaiversion. These changes seem correct and necessary for the release. (Severity: Low - No comment added per review settings) - MCP Optional Dependencies: The addition of
fastapianduvicornto themcpoptional dependency group insrc/praisonai-agents/pyproject.tomlis noted. This change likely supports the new MCP SSE/STDIO features mentioned in the PR title and seems appropriate for the functionality. (Severity: Low - No comment added per review settings) - Hardcoded Version in Deployment Script: The
praisonaiversion is hardcoded in thecreate_dockerfilemethod withinpraisonai/deploy.py. While the version is correctly updated in this PR, hardcoding versions can lead to inconsistencies if the main project version changes. Consider reading the version dynamically frompyproject.tomlin the future to keep this script automatically in sync with the project version. (Severity: Low - No comment added per review settings)
Merge Readiness
Based on the review of the provided diffs, there are no critical, high, or medium severity issues found. The changes primarily involve version updates and dependency additions that seem necessary for the new features. The documentation is also updated. The pull request appears ready to be merged, although I am unable to approve it directly. Please ensure other reviewers have approved this code before merging.
![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
🧹 Nitpick comments (9)
src/praisonai-agents/pyproject.toml (1)
21-23: Review optional dependency duplication.You’ve added
mcp>=1.6.0to themcpoptional group, but it’s already in the basedependencies. Consider removing it to avoid redundancy:mcp = [ - "mcp>=1.6.0", "fastapi>=0.115.0", "uvicorn>=0.34.0" ]docker/Dockerfile.ui (1)
16-16: Approve version bump for UI Dockerfile.Updating
"praisonai==2.2.0"is consistent with the release. For readability, you may standardize quoting across all package specs (e.g., remove quotes around all entries or add quotes uniformly).praisonai/deploy.py (1)
59-59: Approve Dockerfile generation update.The generated
Dockerfilenow installspraisonai==2.2.0, matching other Dockerfiles. Optionally, pinflask,gunicorn, andmarkdownto specific versions to ensure reproducible builds.docker/Dockerfile.chat (1)
16-16: Approve version bump for Chat Dockerfile.Pinning
praisonai==2.2.0here is correct. As a minor nitpick, consider unifying how you quote versioned packages for consistency across Dockerfiles.docker/Dockerfile.dev (1)
17-17: Pinpraisonai_toolsfor reproducibility
Consider adding an explicit version forpraisonai_toolsto lock in a tested release and prevent unexpected upgrades.docker/Dockerfile (1)
4-4: Version bump forpraisonaiin production image
The main Dockerfile now pinspraisonai==2.2.0, which aligns with the library’s version bump. Consider also pinningmarkdown(and any other key libs) to ensure reproducible builds.docs/ui/chat.mdx (1)
158-158: Align chat Dockerfile.dev with version bump
The snippet now usespraisonai==2.2.0. For end-to-end consistency, you might install the chat extra directly (praisonai[chat]==2.2.0) or mirror dependencies from your primary Dockerfile.dev.docs/ui/code.mdx (1)
211-211: Update Code interface Dockerfile.dev snippet
The Code UI docs pinpraisonai==2.2.0as intended. Optionally, specify thecodeextra (praisonai[code]==2.2.0) and lock thewatchdogversion for a more deterministic setup.pyproject.toml (1)
1-280:Details
❓ Verification inconclusive
CI failed: lock file needs regeneration
The pipeline error indicatespoetry.lockis out of sync with these dependency changes. Please runpoetry lockand commit the updatedpoetry.lockto resolve the failure.
🏁 Script executed:
#!/usr/bin/env bash # Regenerate Poetry lock file after version/dependency bumps poetry lockLength of output: 110
CI failed: lock file needs regeneration
The pipeline indicates thatpoetry.lockis out of sync with your updatedpyproject.toml. Since thepoetryCLI isn’t available in this environment, please regenerate the lock file locally and commit it:poetry lock git add poetry.lock git commit -m "Regenerate poetry.lock after dependency/version update"🧰 Tools
🪛 GitHub Actions: Run specific unittest
[error] 1-1: pyproject.toml changed significantly since poetry.lock was last generated. Run
poetry lockto fix the lock file.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
⛔ Files ignored due to path filters (2)
src/praisonai-agents/uv.lockis excluded by!**/*.lockuv.lockis excluded by!**/*.lock
📒 Files selected for processing (11)
docker/Dockerfile(1 hunks)docker/Dockerfile.chat(1 hunks)docker/Dockerfile.dev(1 hunks)docker/Dockerfile.ui(1 hunks)docs/api/praisonai/deploy.html(1 hunks)docs/developers/local-development.mdx(1 hunks)docs/ui/chat.mdx(1 hunks)docs/ui/code.mdx(1 hunks)praisonai/deploy.py(1 hunks)pyproject.toml(4 hunks)src/praisonai-agents/pyproject.toml(2 hunks)
🧰 Additional context used
🪛 GitHub Actions: Run specific unittest
src/praisonai-agents/pyproject.toml
[error] 1-1: pyproject.toml changed significantly since poetry.lock was last generated. Run poetry lock to fix the lock file.
pyproject.toml
[error] 1-1: pyproject.toml changed significantly since poetry.lock was last generated. Run poetry lock to fix the lock file.
🪛 LanguageTool
docs/developers/local-development.mdx
[grammar] ~30-~30: There seems to be a noun/verb agreement error. Did you mean “installs” or “installed”?
Context: ...1-slim WORKDIR /app COPY . . RUN pip install flask praisonai==2.2.0 watchdog EXPOSE...
(SINGULAR_NOUN_VERB_AGREEMENT)
🔇 Additional comments (9)
docs/developers/local-development.mdx (1)
30-30: Approve update to Dockerfile.dev install command.Pinning
praisonaito2.2.0here aligns with the project’s new release. No further changes needed in this snippet.🧰 Tools
🪛 LanguageTool
[grammar] ~30-~30: There seems to be a noun/verb agreement error. Did you mean “installs” or “installed”?
Context: ...1-slim WORKDIR /app COPY . . RUN pip install flask praisonai==2.2.0 watchdog EXPOSE...(SINGULAR_NOUN_VERB_AGREEMENT)
docker/Dockerfile.dev (1)
18-22: Version bump ofpraisonaiand its extras
Thepraisonaipackage has been correctly updated to2.2.0, along with its extras ([ui],[chat],[realtime]).docs/api/praisonai/deploy.html (1)
113-113: Updatepraisonaiversion in generated Dockerfile template
TheCloudDeployernow writesRUN pip install flask praisonai==2.2.0 gunicorn markdown, matching the project’s version bump.pyproject.toml (6)
3-3: Bump project version to 2.2.0
Updating the[project]section version aligns with the PR objective to release v2.2.0.
15-15: Upgradepraisonaiagentsto ≥0.0.83
This matches the companion bump in thesrc/praisonai-agentspackage. Good alignment across modules.
19-19: Relaxmcpconstraint to ≥1.6.0
Changing from==1.6.0to>=1.6.0may pull in newer minor or patch releases—please verify there are no breaking changes in the latestmcpversions.
92-92: Bump Poetry package version to 2.2.0
Mirrors the[project]version bump under the[tool.poetry]section for consistency.
110-110: Upgrade Poetry dependencypraisonaiagentsto ≥0.0.83
Consistent with the top‐leveldependenciessection.
114-114: Relax Poetry constraint formcpto ≥1.6.0
As above, please confirm compatibility with any newermcpreleases imported by this change.
| [project] | ||
| name = "praisonaiagents" | ||
| version = "0.0.82" | ||
| version = "0.0.83" |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Confirm version bump consistency and regenerate lock file.
The version was incremented from 0.0.82 to 0.0.83. CI is failing due to a stale lock file—please regenerate it to align with this change.
Run:
and commit the updated lock file.
🏁 Script executed:
poetry lockLength of output: 110
🏁 Script executed:
# Inspect the locked package metadata to verify the version bump
grep -n '^version = ' poetry.lock || echo "No version lines found in poetry.lock"
head -n 20 poetry.lockLength of output: 9177
🏁 Script executed:
# Locate all project manifest and lock files to verify where version bumps should be applied
find . -type f -name 'pyproject.toml'
find . -type f -name 'poetry.lock'Length of output: 141
🏁 Script executed:
# Check if the root pyproject.toml references the praisonai‐agents subproject
grep -R 'src/praisonai-agents' -n pyproject.toml
# List all path dependencies in root pyproject.toml
grep -R 'path\s*=' -n pyproject.toml
# Show the top of the root pyproject.toml for context
head -n 100 pyproject.tomlLength of output: 2851
🏁 Script executed:
# Verify if praisonaiagents is present in the lock file and its pinned version
grep -R 'name = "praisonaiagents"' -n poetry.lock -A1 || echo "praisonaiagents not found in lock file"Length of output: 109
Regenerate the lock file to bump praisonaiagents to 0.0.83
The root poetry.lock still pins praisonaiagents at 0.0.71, but your pyproject.toml now requires praisonaiagents>=0.0.83. Please run:
poetry update praisonaiagents
# or simply
poetry lockand commit the updated poetry.lock so that the pinned version matches your version bump.
• Location: poetry.lock (line ~6051 shows version = "0.0.71")
• Ensure praisonaiagents is updated to 0.0.83 in the lock file.
🤖 Prompt for AI Agents
In src/praisonai-agents/pyproject.toml at line 7, the version was bumped to
0.0.83 but the root poetry.lock file still pins praisonaiagents at 0.0.71,
causing CI failures. To fix this, run 'poetry update praisonaiagents' or 'poetry
lock' in the root directory to regenerate the lock file with the updated version
0.0.83, then commit the updated poetry.lock file to ensure version consistency.
| @@ -15,7 +15,7 @@ RUN apt-get update && apt-get install -y --no-install-recommends \ | |||
| RUN pip install --no-cache-dir \ | |||
| praisonaiagents>=0.0.4 \ | |||
There was a problem hiding this comment.
🛠️ Refactor suggestion
Mismatch of praisonaiagents version
The base image still installs praisonaiagents>=0.0.4, but your pyproject.toml bumps it to 0.0.83. Please align this pin to avoid pulling an older release.
Apply:
- praisonaiagents>=0.0.4 \
+ praisonaiagents>=0.0.83 \📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| praisonaiagents>=0.0.4 \ | |
| praisonaiagents>=0.0.83 \ |
🤖 Prompt for AI Agents
In docker/Dockerfile.dev at line 16, the version of praisonaiagents is pinned to
>=0.0.4, which conflicts with the updated version 0.0.83 specified in
pyproject.toml. Update the version specifier in the Dockerfile.dev to
praisonaiagents>=0.0.83 to ensure consistency and avoid installing an older
release.
v2.2 with MCP SSE and STDIO
1 participant
Summary by CodeRabbit