Update version to 2.2.15 across project files#517
Conversation
- Incremented PraisonAI version from 2.2.14 to 2.2.15 in `pyproject.toml`, `uv.lock`, and all relevant Dockerfiles for consistency. - Updated dependency version for `praisonaiagents` from 0.0.87 to 0.0.88. - Ensured minimal changes to existing code while maintaining versioning accuracy across the project.
|
Caution Review failedThe pull request is closed. WalkthroughThe changes update the version of the Changes
Possibly related PRs
Suggested labels
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (11)
✨ 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-code-assist here to provide a summary of this pull request. This PR focuses on a routine version update for the project. The main goal is to increment the core PraisonAI version to 2.2.15 and update the dependency on praisonaiagents to version 0.0.88. These version bumps are propagated across various configuration files, lock files, Dockerfiles, and documentation examples to ensure consistency throughout the project.
Highlights
- Main Project Version Update: The primary version of the
PraisonAIproject has been updated from2.2.14to2.2.15in thepyproject.tomlanduv.lockfiles. - Dependency Version Update: The required version for the
praisonaiagentsdependency has been updated from>=0.0.87to>=0.0.88in the mainpyproject.tomlanduv.lock. The version within thesrc/praisonai-agentssub-project'spyproject.tomlanduv.lockhas also been incremented to0.0.88. - Consistent Versioning Across Files: References to the
praisonaipackage version have been updated to2.2.15in all relevant Dockerfiles (docker/Dockerfile,docker/Dockerfile.chat,docker/Dockerfile.dev,docker/Dockerfile.ui), documentation examples (docs/api/praisonai/deploy.html,docs/developers/local-development.mdx,docs/ui/chat.mdx,docs/ui/code.mdx), and the Python script that generates a Dockerfile (praisonai/deploy.py).
Changelog
Click here to see the changelog
- docker/Dockerfile
- Updated
praisonaiversion from2.2.14to2.2.15in thepip installcommand (line 4).
- Updated
- docker/Dockerfile.chat
- Updated
praisonaiversion from2.2.14to2.2.15in thepip installcommand (line 16).
- Updated
- docker/Dockerfile.dev
- Updated
praisonaiversion from2.2.14to2.2.15in thepip installcommand (line 18).
- Updated
- docker/Dockerfile.ui
- Updated
praisonaiversion from2.2.14to2.2.15in thepip installcommand (line 16).
- Updated
- docs/api/praisonai/deploy.html
- Updated
praisonaiversion from2.2.14to2.2.15in the embedded Dockerfile example string (line 113).
- Updated
- docs/developers/local-development.mdx
- Updated
praisonaiversion from2.2.14to2.2.15in the Dockerfile example (line 30).
- Updated
- docs/ui/chat.mdx
- Updated
praisonaiversion from2.2.14to2.2.15in the Dockerfile example (line 158).
- Updated
- docs/ui/code.mdx
- Updated
praisonaiversion from2.2.14to2.2.15in the Dockerfile example (line 211).
- Updated
- praisonai/deploy.py
- Updated
praisonaiversion from2.2.14to2.2.15in the generated Dockerfile content string (line 59).
- Updated
- pyproject.toml
- Updated
project.versionfrom2.2.14to2.2.15(line 3). - Updated
dependencies.praisonaiagentsrequirement from>=0.0.87to>=0.0.88(line 15). - Updated
tool.poetry.versionfrom2.2.14to2.2.15(line 92). - Updated
tool.poetry.dependencies.praisonaiagentsrequirement from>=0.0.87to>=0.0.88(line 110).
- Updated
- src/praisonai-agents/pyproject.toml
- Updated
project.versionfrom0.0.87to0.0.88(line 7).
- Updated
- src/praisonai-agents/uv.lock
- Updated
package.praisonaiagents.versionfrom0.0.87to0.0.88(line 1460). - Updated sdist and wheel URLs, hashes, and sizes for
praisonaiagents.
- Updated
- uv.lock
- Updated
package.praisonai.versionfrom2.2.14to2.2.15(line 3617). - Updated
requires-dist.praisonaiagentsrequirement from>=0.0.87to>=0.0.88(line 3759). - Updated
package.praisonaiagents.versionfrom0.0.87to0.0.88(line 3816). - Updated sdist and wheel URLs, hashes, and sizes for
praisonaiagents.
- 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.
Versions align now,
From two point two point fourteen,
To two point two fifteen.
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 PR correctly updates the PraisonAI version to 2.2.15 and the praisonaiagents dependency to 0.0.88 across the specified project files. The changes are consistent and align with the PR's objective.
I have one suggestion regarding how the PraisonAI version is specified in the praisonai/deploy.py script to improve long-term maintainability. Other minor points about version hardcoding in documentation examples are noted in the summary but are of low severity, and thus not commented on directly per review settings.
Summary of Findings
- Hardcoded Version in Deployment Script: The file
praisonai/deploy.pyhardcodes thePraisonAIversion string when generating Dockerfile content. This is a maintainability concern (medium severity) and has been commented on. - Hardcoded Versions in Documentation Examples: Several documentation files (
.mdxfiles:docs/developers/local-development.mdx,docs/ui/chat.mdx,docs/ui/code.mdx) contain hardcodedPraisonAIversions in example Dockerfile snippets. While common for examples, this can lead to outdated documentation if not updated consistently with the project version. This is considered low severity and was not commented on directly due to review settings. - Generated HTML Documentation: The file
docs/api/praisonai/deploy.htmlalso contains the hardcoded version. This file appears to be auto-generated based onpraisonai/deploy.py. Ifpraisonai/deploy.pyis updated to use dynamic versioning, this HTML file should reflect the change upon regeneration. This is considered low severity and dependent on thedeploy.pyfix.
Merge Readiness
The pull request effectively updates the version numbers as intended across most files. The changes are largely accurate and consistent.
However, there's a medium-severity maintainability issue in praisonai/deploy.py where the PraisonAI version is hardcoded. Addressing this by dynamically fetching the version would make future version bumps more robust and less error-prone. I've provided a suggestion for this in the review comments.
Given this, I recommend that the suggested improvement in praisonai/deploy.py be considered before merging to enhance long-term maintainability. As an AI reviewer, I am not authorized to approve pull requests; please ensure further review and approval by project maintainers.
| file.write("WORKDIR /app\n") | ||
| file.write("COPY . .\n") | ||
| file.write("RUN pip install flask praisonai==2.2.14 gunicorn markdown\n") | ||
| file.write("RUN pip install flask praisonai==2.2.15 gunicorn markdown\n") |
There was a problem hiding this comment.
The PraisonAI version is hardcoded here as praisonai==2.2.15. This can lead to inconsistencies during future version bumps if this location is missed, requiring manual updates in multiple places.
To improve maintainability, could we fetch this version dynamically? One common approach is to use importlib.metadata.version('PraisonAI') (available in Python 3.8+). This would allow the generated Dockerfile to always use the version of PraisonAI that this script itself belongs to.
For example:
# At the top of praisonai/deploy.py (or within the CloudDeployer class scope)
import importlib.metadata
try:
# Assuming 'PraisonAI' is the correct distribution name as in pyproject.toml
praisonai_pkg_version = importlib.metadata.version('PraisonAI')
except importlib.metadata.PackageNotFoundError:
# Fallback if the package is not found (e.g., during development before installation)
# For this PR, the current version is 2.2.15. A more robust fallback or error handling might be needed.
praisonai_pkg_version = "2.2.15"
# Then, in this line, you could use an f-string:
# file.write(f"RUN pip install flask praisonai=={praisonai_pkg_version} gunicorn markdown\n")This change would make future version updates more robust by having a single source of truth for the version within the generated Dockerfile content.
Update version to 2.2.15 across project files
1 participant
pyproject.toml,uv.lock, and all relevant Dockerfiles for consistency.praisonaiagentsfrom 0.0.87 to 0.0.88.Summary by CodeRabbit
praisonaiPython package to version 2.2.15 across all Docker environments and documentation.praisonaiagentsdependency to version 0.0.88.