Fix leanvec ood for public-only build and update binaries#290
Merged
ethanglaser merged 5 commits intomainfrom Mar 16, 2026
Merged
Fix leanvec ood for public-only build and update binaries#290ethanglaser merged 5 commits intomainfrom
ethanglaser merged 5 commits intomainfrom
Conversation
ethanglaser
requested review from
ahuber21,
homksei,
ibhati,
mihaic and
yuejiaointel
as code owners
ibhati
approved these changes
Mar 16, 2026
ethanglaser
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes public-only cpp runtime bindings validation with lack of equivalent header that was added for private interface use with leanvec ood.
Also allows runtime bindings validation runs to proceed regardless of whether another fails, making it easier to identify root cause of issues.
Lastly, updates CMakeLists.txts for shared examples and cpp runtime bindings to use v0.2.0 binaries as this was investigated initially as a potential cause of the CI issues and should be done anyway