Skip to content

v1.16: Multimodal search #3312

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Jul 31, 2025
Merged

v1.16: Multimodal search #3312

merged 13 commits into from
Jul 31, 2025

Conversation

guimachiavelli
Copy link
Member

Fixes #3298

@guimachiavelli guimachiavelli moved this to Engine release in Code sample changes Jul 23, 2025
@guimachiavelli guimachiavelli linked an issue Jul 23, 2025 that may be closed by this pull request
4 tasks
@guimachiavelli guimachiavelli marked this pull request as ready for review July 23, 2025 16:18
@guimachiavelli guimachiavelli requested a review from a team as a code owner July 23, 2025 16:18
@guimachiavelli guimachiavelli requested a review from dureuill July 23, 2025 16:21
Copy link
Contributor

@dureuill dureuill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like the PR additionally makes changes related to code samples but unrelated to multimodal per se.

I didn't review these changes, only the multimodal ones.

The documentation looks right, I wonder if we should plan a more principled guide on how to setup a multimodal embedder with Voyage as backend 🤔

@guimachiavelli
Copy link
Member Author

I should have mentioned that you needed not mind the code sample changes. They're a kink we haven't been able to iron out yet in our Mintlify workflow. Apologies for that, but, yes, I expected you to ignore them.

Regarding the guide, yes, that is something I think is necessary, but with everything happening internally I wasn't able to make the time for it before the release. 😢

@Strift
Copy link
Contributor

Strift commented Jul 30, 2025

Since we have an existing Voyage AI guide, maybe a quick win would be adding a "Multi-modal embeddings" section there? It could simply pull from the release notes example implementation?

@guimachiavelli
Copy link
Member Author

Hmmm…that's not a bad idea, but after some thought I don't see a good way of integrating a multimodal section that doesn't make the current guide worse. at least not without rewriting significant chunks, at which point we're not really saving any time.

I spoke about this with Guillaume and I'll make the time to write a dedicated bit of content for this after the engine release, but before the marketing launch in September.

@guimachiavelli guimachiavelli merged commit 9fc49d6 into v1.16 Jul 31, 2025
3 of 4 checks passed
@guimachiavelli guimachiavelli deleted the v1.16-3298-multimodal-search branch July 31, 2025 12:41
guimachiavelli added a commit that referenced this pull request Aug 4, 2025
* bump version number

* v1.16: Telemetry updates (#3325)

* v1.16: Experimental: Disable new indexer (#3313)

* v1.16: Bump Docker image tag version (#3323)

* v1.16: Add `sort` parameter to `/documents` route (#3318)

* v1.16: `rankingScoreThreshold` no longer affects `totalHits` accuracy (#3322)

* V1.16: Update `/batches` response (#3314)

* v1.16: Update Postman collection (#3324)

* v1.15.1: `/chat` route docs review (#3316)

* fix /network route component

* v1.16: `/export` route (#3315)

* v1.16: Multimodal search (#3312)

---------

Co-authored-by: macraig <[email protected]>
Co-authored-by: Mubelotix <[email protected]>
Co-authored-by: Clément Renault <[email protected]>
Co-authored-by: Louis Dureuil <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Engine release
Development

Successfully merging this pull request may close these issues.

v1.16: Experimental: Multimodal search
3 participants