Repository navigation
SEARCH-3102 add semantic search to bdk (#374) - #402
Merged
sebastientosello merged 11 commits intoSep 10, 2026
Merged
sebastientosello merged 11 commits into
sebastientosello merged 11 commits into
Conversation
broHeryk
force-pushed
the
SEARCH-3102-semantic-search-3x
branch
from
September 1, 2026 14:36
3ba4ebc to
3a439fd
Compare
broHeryk
changed the title
broHeryk
force-pushed
the
SEARCH-3102-semantic-search-3x
branch
from
September 2, 2026 08:10
13c3b1d to
ac7a29e
Compare
matthewcummings
self-requested a review
September 4, 2026 15:49
Contributor
|
Lets take a different path to get 3.x aligned with main branch and ship the semantic search bit. Here is what we can do ;
|
* Raise cryptography ceiling to allow the patched 50.x The current constraint, cryptography>=48.0.1,<49.0.0, cannot resolve to a version free of known CVEs: 48.0.1 CVE-2026-69247 and CVE-2026-69249 49.0.0 CVE-2026-69247 50.0.x clean Both CVEs were published 2026-08-03, before 2.11.3 was released, so every version the released constraint permits is affected. Downstream consumers cannot work around this: anything satisfying the BDK is vulnerable, and anything patched fails resolution. It surfaces as a hard failure in image compliance scanning. This is the second time in eight days the ceiling has blocked a security fix. finos#397 raised it from <47.0.0 to <49.0.0 for CVE-2026-34180, and it is already stale again. Verified: the full test suite passes on the new lock and identically on the old pin, so this is not masking a regression. cryptography 48.0.1 560 passed, 3 skipped cryptography 50.0.0 560 passed, 3 skipped cryptography 50.0.1 560 passed, 3 skipped (the locked version) poetry.lock regenerated with Poetry 2.4.2; cryptography 48.0.1 to 50.0.1 is the only package change, none added or removed. * Bump version to 2.11.4 to prepare a patch release Included here so merging this PR leaves main release-ready, rather than needing a second PR before the fix can reach consumers. The constraint fix in finos#390 sat unreleased for five days because the version bump was a separate change (finos#397). The CVEs this PR addresses are live in the released 2.11.3, so the gap matters. Follows the same convention as finos#397: pyproject.toml only. The lock is unaffected, project version is not part of its content hash. (cherry picked from commit 487ac1c)
broHeryk
force-pushed
the
SEARCH-3102-semantic-search-3x
branch
2 times, most recently
from
September 9, 2026 15:42
77c2bfe to
8784fad
Compare
broHeryk
force-pushed
the
SEARCH-3102-semantic-search-3x
branch
from
September 9, 2026 15:56
8784fad to
ebfb75c
Compare
sebastientosello
approved these changes
Sep 10, 2026
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
3 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.
Description
Closes SEARCH-3102
We've got ability to use semantic search instead alongside exact match search. This PR adds a method to handle it.
Dependencies
None
Checklist