Summary
cognee 1.1.2 declares an exact pin Requires-Dist: ladybug==0.16.0. This hard pin blocks any environment that needs a newer ladybug (currently 0.17.1, with 0.16.1 also available) and triggers resolver conflicts in mixed conda/PyPI setups.
Environment
- cognee 1.1.2, Python 3.13, macOS arm64 (managed via
pixi / uv)
Impact
Because cognee pins ladybug==0.16.0, downstream projects must pin ladybug==0.16.0 everywhere, which (a) prevents picking up ladybug patch/minor fixes and (b) causes dependency-resolution failures when another constraint in the environment wants a newer ladybug. We currently have to carry an explicit ladybug==0.16.0 in our manifest solely to match cognee.
Likely cause
This appears tied to the internal ladybug_version_mapping (cf. closed #2768). If the mapping is version-coupled, newer ladybug releases need a corresponding mapping entry.
Request
- Add
ladybug_version_mapping entries for 0.16.1 and 0.17.1.
- Relax the dependency from
==0.16.0 to a tested range (e.g. >=0.16.0,<0.18).
Happy to test or open a PR
Summary
cognee1.1.2 declares an exact pinRequires-Dist: ladybug==0.16.0. This hard pin blocks any environment that needs a newerladybug(currently 0.17.1, with 0.16.1 also available) and triggers resolver conflicts in mixed conda/PyPI setups.Environment
pixi/uv)Impact
Because cognee pins
ladybug==0.16.0, downstream projects must pinladybug==0.16.0everywhere, which (a) prevents picking up ladybug patch/minor fixes and (b) causes dependency-resolution failures when another constraint in the environment wants a newerladybug. We currently have to carry an explicitladybug==0.16.0in our manifest solely to match cognee.Likely cause
This appears tied to the internal
ladybug_version_mapping(cf. closed #2768). If the mapping is version-coupled, newer ladybug releases need a corresponding mapping entry.Request
ladybug_version_mappingentries for 0.16.1 and 0.17.1.==0.16.0to a tested range (e.g.>=0.16.0,<0.18).Happy to test or open a PR