Skip to content
CI

feat!: rename bm25 APIs to paradedb and always use the paradedb access method #192

Sign in to view logs

feat!: rename bm25 APIs to paradedb and always use the paradedb access method

feat!: rename bm25 APIs to paradedb and always use the paradedb access method #192

Triggered via pull request July 27, 2026 16:01
@rebasedmingrebasedming
synchronize #91
paradedb-am
Status Success
Total duration 2m 7s
Artifacts –

ci.yml

on: pull_request
Lint
36s
Lint
Windows Smoke
1m 45s
Windows Smoke
Check API Coverage
11s
Check API Coverage
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Check API Coverage
No file matched to [/home/runner/work/efcore-paradedb/efcore-paradedb/**/*requirements*.txt,/home/runner/work/efcore-paradedb/efcore-paradedb/**/*requirements*.in,/home/runner/work/efcore-paradedb/efcore-paradedb/**/*constraints*.txt,/home/runner/work/efcore-paradedb/efcore-paradedb/**/*constraints*.in,/home/runner/work/efcore-paradedb/efcore-paradedb/**/pyproject.toml,/home/runner/work/efcore-paradedb/efcore-paradedb/**/uv.lock,/home/runner/work/efcore-paradedb/efcore-paradedb/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.