Update mixedbread embeddings and rerank

[joeldierkes]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

commit 3e4cb07

chore: update the rerank mixedbread version

Calling the mixedbread rerank currently yields a "503 Service
Temporary Unavailable". The current version of the mixedbread client
used is deprecated and not compatible with the api anymore.

Let's use the new "mixedbread" pypi package which is the supported
Mixedbread python client. This client is mostly compatible with the
old one, except that the TruncationStrategy got removed.

For backwards-compatibility the llama-index-integration will remain
named mixedbreadai.

commit df04159

chore: update the embeddings mixedbread version

Calling the mixedbread embedding currently yields a "503 Service
Temporary Unavailable". The current version of the mixedbread client
used is deprecated and not compatible with the api anymore.

Let's use the new "mixedbread" pypi package which is the supported
Mixedbread python client. This client is mostly compatible with the
old one, except that the TruncationStrategy got removed.

For backwards-compatibility the llama-index-integration will remain
named mixedbreadai.

New Package?

Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

• Yes
• No

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

• Yes
• No

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update (maybe, the notebooks have been updated?)

How Has This Been Tested?

Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

• I added new unit tests to cover this change
• I believe this change is already covered by existing unit tests (and I changed the tests accordingly)

Suggested Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added Google Colab support for the newly added notebooks.
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I ran uv run make format; uv run make lint to appease the lint gods

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB