You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both jobs ran current CI against the frozen `integrations/openai` /
`integrations/langchain` source from historical tags (databricks-ai-
v0.2.0 through v0.5.0). They worked while PyPI dep evolution was
backward-compatible.
That contract broke with the databricks-vectorsearch → databricks-ai-
search rename. The frozen historical sources import VectorSearchIndex
from `databricks.vector_search.client` (the path that was removed in
the rename), and there's no PR to HEAD that can update that frozen
source. The matrix is permanently red regardless of what HEAD does.
Per Ann: "we can restart them from the version we are deploying."
Remove both jobs now; once we ship a release containing the ai-search
migration (#437), the cross-version matrix can be re-introduced with
that release as the new stable baseline.
The bridge's own unit tests + integration tests still cover regression
risk. This removes a non-Required CI signal that's now noise rather
than information.
0 commit comments