[BUG] crewai install brings in crewai-tools

[ciarancourtney]

Description

Docs say crewai-tools are an optional dependency, the pyproject seems to confirm that but the whl metadata says otherwise

Steps to Reproduce

1. pip install crewai

Expected behavior

crewai-tools is not installed

Screenshots/Code snippets

n/a

Operating System

Other (specify in additional context)

Python Version

3.10

crewAI Version

latest

crewAI Tools Version

n/a

Virtual Environment

Venv

Evidence

curl https://files.pythonhosted.org/packages/c8/04/3808fe66acabebc5b5dcf00e4f290ae67a817d18ad96b043dd9769f51da8/crewai-0.86.0-py3-none-any.whl.metadata | grep tools -B30
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Metadata-Version: 2.3
Name: crewai
Version: 0.86.0
Summary: Cutting-edge framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.
Project-URL: Homepage, https://crewai.com
Project-URL: Documentation, https://docs.crewai.com
Project-URL: Repository, https://github.com/crewAIInc/crewAI
Author-email: Joao Moura <[email protected]>
Requires-Python: <=3.13,>=3.10
Requires-Dist: appdirs>=1.4.4
Requires-Dist: auth0-python>=4.7.1
Requires-Dist: chromadb>=0.5.18
Requires-Dist: click>=8.1.7
Requires-Dist: crewai-tools>=0.17.0                 <<<<<<<<<<<<< here
Requires-Dist: instructor>=1.3.3
Requires-Dist: json-repair>=0.25.2
Requires-Dist: jsonref>=1.1.0
Requires-Dist: litellm>=1.44.22
Requires-Dist: openai>=1.13.3

Possible Solution

?

Additional context

n/a

[joaoigm]

@ciarancourtney I found out that crewai-tools was listed as an optional dependency and dev dependency. Pip install doesn't distinguish between main dependencies and dev dependencies, so crewai-tools is always installed.

I already have a PR ready to fix this issue.

[ciarancourtney]

Thats odd, it makes me think its actually something else, either a bug with uv publish or something wrong with the CI pipeline that ends up merging the dev dependencies with main dependencies

[joaoigm]

I tested the command uv export. If I don`t explicitly tell uv not to export dev dependencies, it will be included on requirements.txt. I think that UV Publish follows the same logic

[joaoigm]

Also, I didn't find a workflow that publishes the package, so I think it is published manually