fix: adapt our implementation to breaking changes in Chroma 0.5.17 - Githubissues

deepset-ai / haystack-core-integrations

Additional packages (components, document stores and the likes) to extend the capabilities of Haystack version 2.0 and onwards

https://haystack.deepset.ai

Apache License 2.0

121 stars 119 forks source link

fix: adapt our implementation to breaking changes in Chroma 0.5.17 #1165

Closed anakin87 closed 2 weeks ago

anakin87 commented 2 weeks ago

Related Issues

failing tests: https://github.com/deepset-ai/haystack-core-integrations/actions/runs/11655758403
in 0.5.17, Chroma introduced some breaking changes:
- writing documents that do not contain a valid string (None) causes an error
- they changed filter default: from {} to None

Proposed Changes:

incorporate their changes
pin chroma>=0.5.17

How did you test it?

CI

Checklist

I have read the contributors guidelines and the code of conduct
I have updated the related issue with new insights and changes
I added unit tests and updated the docstrings
I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.