chore: update PraisonAI version to 2.2.20 across Dockerfiles and docu…#553
chore: update PraisonAI version to 2.2.20 across Dockerfiles and docu…#553MervinPraison merged 1 commit intomainfrom
Conversation
…mentation - Updated the version of PraisonAI from 2.2.19 to 2.2.20 in all relevant Dockerfiles. - Adjusted README and local development documentation to reflect the new version. - Ensured consistency in versioning across all instances where PraisonAI is referenced.
|
Warning Rate limit exceeded@MervinPraison has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 49 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (12)
✨ 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 (
|
✅ Deploy Preview for praisonai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![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 is a chore update focused on bumping the version of the praisonai package used throughout the project. The primary goal is to upgrade from version 2.2.19 to 2.2.20 and ensure this change is reflected consistently across all relevant configuration files, Docker images, and documentation.
Highlights
- PraisonAI Version Bump: The core change involves updating the required version of the
praisonaiPython package to2.2.20. - Widespread Configuration Updates: This version update is applied across multiple files, including various Dockerfiles, the main Docker README, documentation files (Markdown and HTML), the project's
pyproject.toml, and theuv.lockfile, ensuring all references point to the new version. - Homebrew Formula Update: The Homebrew formula for PraisonAI (
praisonai.rb) has also been updated to fetch thev2.2.20release tarball and includes the corresponding updated SHA256 hash.
Changelog
Click here to see the changelog
- docker/Dockerfile
- Updated
praisonaiversion requirement from>=2.2.19to>=2.2.20on line 19.
- Updated
- docker/Dockerfile.chat
- Updated
praisonaiversion requirement from>=2.2.19to>=2.2.20on line 19.
- Updated
- docker/Dockerfile.dev
- Updated
praisonaiversion requirement from>=2.2.19to>=2.2.20on line 23.
- Updated
- docker/Dockerfile.ui
- Updated
praisonaiversion requirement from>=2.2.19to>=2.2.20on line 19.
- Updated
- docker/README.md
- Updated the listed PraisonAI version from
>=2.2.19to>=2.2.20under 'Package Versions' on line 124. - Updated the version pinning example from
==2.2.19to==2.2.20on line 221.
- Updated the listed PraisonAI version from
- docs/api/praisonai/deploy.html
- Updated the
praisonaiversion in the example Dockerfile snippet from==2.2.19to==2.2.20on line 113.
- Updated the
- docs/developers/local-development.mdx
- Updated the
praisonaiversion in the example Dockerfile snippet from==2.2.19to==2.2.20on line 30.
- Updated the
- docs/ui/chat.mdx
- Updated the
praisonaiversion in the example Dockerfile snippet from==2.2.19to==2.2.20on line 158.
- Updated the
- docs/ui/code.mdx
- Updated the
praisonaiversion in the example Dockerfile snippet from==2.2.19to==2.2.20on line 211.
- Updated the
- src/praisonai/praisonai.rb
- Updated the download URL for the Homebrew formula to reference
v2.2.20on line 6. - Updated the SHA256 checksum to match the
v2.2.20tarball on line 7.
- Updated the download URL for the Homebrew formula to reference
- src/praisonai/praisonai/deploy.py
- Updated the
praisonaiversion string used when generating a Dockerfile from==2.2.19to==2.2.20on line 59.
- Updated the
- src/praisonai/pyproject.toml
- Updated the project version from
2.2.19to2.2.20in the[project]section on line 3. - Updated the project version from
2.2.19to2.2.20in the[tool.poetry]section on line 97.
- Updated the project version from
- src/praisonai/uv.lock
- Updated the locked version of
praisonaifrom2.2.19to2.2.20on line 3934.
- Updated the locked version of
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.
Version number climbs,
Docs and code now match the tag,
Sync is complete.
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. ↩
There was a problem hiding this comment.
Code Review
This pull request effectively updates the PraisonAI version to 2.2.20 across various Dockerfiles, documentation, and package configuration files. The changes are consistent and appear to cover all necessary locations. Great job on the thoroughness of these updates!
Summary of Findings
- Homebrew Formula SHA256 Calculation: The
praisonai.rbHomebrew formula uses a dynamiccurlandshasumcommand to determine thesha256checksum for the new version2.2.20. This approach relies on thev2.2.20tag and its release tarball being immediately available and stable at the specified URL upon merging this PR. If there's a delay or issue with the release, Homebrew installations could fail due to checksum mismatches or inability to download the source. It's important to coordinate the release of thev2.2.20tag with this formula update.
Merge Readiness
The pull request is well-executed for updating the PraisonAI version to 2.2.20 across the codebase and documentation. The changes are consistent and thorough. There is one point regarding the Homebrew formula's dynamic SHA256 calculation that should be confirmed: please ensure the v2.2.20 tag and release tarball are available before this change is widely used to prevent potential installation issues for Homebrew users. Otherwise, the PR looks good. As an AI, I am not authorized to approve pull requests, so please ensure further review and approval by authorized maintainers before merging.
| url "https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.19.tar.gz" | ||
| sha256 `curl -sL https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.19.tar.gz | shasum -a 256`.split.first | ||
| url "https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.20.tar.gz" | ||
| sha256 `curl -sL https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.20.tar.gz | shasum -a 256`.split.first |
There was a problem hiding this comment.
The Homebrew formula now dynamically calculates the sha256 checksum for version 2.2.20 at install time. Could you confirm if the Git tag v2.2.20 and its corresponding release tarball at https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.20.tar.gz will be available before this formula change is merged or widely consumed? If the tag or tarball isn't accessible when users attempt to install or update via Homebrew, the curl command will likely fail or fetch incorrect content, leading to a sha256 mismatch and installation failure.
While dynamic SHA calculation is a pattern sometimes used in taps for convenience, ensuring the upstream release is available is crucial for a smooth user experience.
chore: update PraisonAI version to 2.2.20 across Dockerfiles and docu…
1 participant
…mentation