feat: bump versions to 1.14.5a5#5777
Merged
Merged
Conversation
📝 WalkthroughWalkthroughBumps prerelease package versions from 1.14.5a4 → 1.14.5a5 across the repo and expands the Daytona filesystem tool schema and model_config to add actions (exists, move, find, search, chmod, replace) with conditional parameter requirements. ChangesVersion Bump Across All Packages
Daytona File Tool Schema and Implementation
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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 `@lib/crewai/pyproject.toml`:
- Line 57: The manifest pins are inconsistent: crewi-tools is 1.14.5a5 while
crewi-core, crewi-cli and crewi-files remain at 1.14.5a4; pick a single
prerelease and make all internal package pins match — e.g., update the
crewi-core, crewi-cli, and crewi-files entries to "1.14.5a5" so crewi-tools,
crewi-core, crewi-cli, and crewi-files all use the same prerelease version.
🪄 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: Pro Plus
Run ID: 512da59f-da69-407e-beee-127b04f0d9af
📒 Files selected for processing (8)
lib/cli/src/crewai_cli/__init__.pylib/crewai-core/src/crewai_core/__init__.pylib/crewai-files/src/crewai_files/__init__.pylib/crewai-tools/pyproject.tomllib/crewai-tools/src/crewai_tools/__init__.pylib/crewai/pyproject.tomllib/crewai/src/crewai/__init__.pylib/devtools/src/crewai_devtools/__init__.py
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a3b3d13. Configure here.
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 `@lib/crewai-tools/tool.specs.json`:
- Around line 7429-7441: The JSON schema in tool.specs.json allows invalid
action payloads because it only requires "action" but does not enforce
action-specific required fields described in the comments; update
tool.specs.json to mirror the runtime checks in daytona_file_tool.py by adding
conditional allOf/if-then guards per action (e.g., require "path" for actions
other than "replace", require "move.destination" when action=="move", require
"find.pattern" or "search.pattern" for find/search, require "replace.paths" or
"replace.pattern" and "replace.replacement" for replace, and require at least
one of "mode","owner","group" when action=="chmod"); use the same property names
shown in the diff ("path", "move.destination", "find"/"search"."pattern",
"replace.paths"/"replace.pattern"/"replace.replacement", "chmod") so LLM
integrations validate inputs the same way the `@model_validator` in
daytona_file_tool.py does.
🪄 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: Pro Plus
Run ID: 92ad786c-da3e-4089-992f-3d108a0cc04a
📒 Files selected for processing (1)
lib/crewai-tools/tool.specs.json
Bump crewai-core/crewai-cli/crewai-files pins to 1.14.5a5 in crewai and cli manifests so installs resolve. Encode DaytonaFileToolSchema's runtime action/required-field rules as json_schema_extra so LLM integrations validate against the same constraints.
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
`@lib/crewai-tools/src/crewai_tools/tools/daytona_sandbox_tool/daytona_file_tool.py`:
- Around line 36-87: The schema in _daytona_file_schema_extra currently only
requires presence of fields (path, content, destination, pattern, paths,
mode/owner/group) which allows null/empty values that later fail in
_validate_action_args; update the conditional subschemas to enforce non-null and
non-empty values by adding proper property constraints (e.g., for string fields
set "type":"string" and "minLength":1 or disallow "null", and for array fields
set "type":"array" and "minItems":1) instead of just using "required", and
ensure the chmod branch’s anyOf entries validate the actual field types/values
rather than merely their presence so schema-level validation matches
_validate_action_args behavior.
🪄 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: Pro Plus
Run ID: 7aaf413f-a78d-410a-9750-6e4b872a9010
📒 Files selected for processing (4)
lib/cli/pyproject.tomllib/crewai-tools/src/crewai_tools/tools/daytona_sandbox_tool/daytona_file_tool.pylib/crewai-tools/tool.specs.jsonlib/crewai/pyproject.toml
✅ Files skipped from review due to trivial changes (1)
- lib/cli/pyproject.toml
🚧 Files skipped from review as they are similar to previous changes (1)
- lib/crewai-tools/tool.specs.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Medium Risk
Medium risk because
DaytonaFileToolgains new filesystem-manipulation actions (chmod,replace,move, etc.) and changes argument schema/validation, which could affect tool-call compatibility and sandbox side effects.Overview
Bumps package versions and intra-repo dependency pins across
crewai,crewai-core,crewai-cli,crewai-files,crewai-tools, anddevtoolsto1.14.5a5.Expands
DaytonaFileToolto support additional filesystem operations (exists,move,find,search,chmod,replace) and updates the tool’s JSON schema (tool.specs.json) to use conditional required fields (e.g.,destinationformove,patternforfind/search, andpaths/pattern/replacementforreplace), with related parameter description/nullable-field adjustments.Reviewed by Cursor Bugbot for commit 06010b2. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
New Features
Chores