langchain-apify currently pins apify-client = "^2.3.0" (i.e. >= 2.3.0, < 3.0.0), which prevents it from being installed alongside anything that requires apify-client v3.
Impact
Apify Python SDK v4 requires apify-client >= 3.1.0. Because langchain-apify caps apify-client < 3.0.0, any project depending on both cannot resolve. This blocks upgrading the python-crewai Actor template — whose ApifyActorsTool (from crewai-tools) is backed by langchain-apify — to Apify SDK v4.
Resolution error from uv:
Because langchain-apify>=0.1.6 depends on apify-client>=2.3.0,<3.0.0
and apify>=4.0.0 depends on apify-client[brotli]>=3.1.0, we can conclude
that apify>=4.0.0 and all versions of langchain-apify are incompatible.
Action
Widen the constraint to support apify-client v3 (apify-client (>=3.0.0,<4.0.0)) and adapt to its breaking changes — most notably the fully-typed clients, where resource methods now return Pydantic models (e.g. Run, DatasetItemsPage) instead of dicts, so run['defaultDatasetId']-style access becomes run.default_dataset_id.
Related
✍️ Drafted by Claude Code
langchain-apifycurrently pinsapify-client = "^2.3.0"(i.e.>= 2.3.0, < 3.0.0), which prevents it from being installed alongside anything that requiresapify-clientv3.Impact
Apify Python SDK v4 requires
apify-client >= 3.1.0. Becauselangchain-apifycapsapify-client < 3.0.0, any project depending on both cannot resolve. This blocks upgrading thepython-crewaiActor template — whoseApifyActorsTool(fromcrewai-tools) is backed bylangchain-apify— to Apify SDK v4.Resolution error from uv:
Action
Widen the constraint to support
apify-clientv3 (apify-client (>=3.0.0,<4.0.0)) and adapt to its breaking changes — most notably the fully-typed clients, where resource methods now return Pydantic models (e.g.Run,DatasetItemsPage) instead of dicts, sorun['defaultDatasetId']-style access becomesrun.default_dataset_id.Related
python-crewaitemplate's SDK v4 bump.✍️ Drafted by Claude Code