mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-16 07:36:50 +00:00
Current release status: hold for the independently reproduced LargeList reader regression in https://github.com/lancedb/lancedb/pull/4712#discussion_r4409195229. All 54 CI checks passed at `a26e461b86728f7e7977f1c221af70a32033a144`; passing CI does not clear that compatibility finding. The Java artifact availability finding is fixed: the official Lance Maven mirror and Maven Central now serve the 14.0.2 POM and JAR (HTTP 200). [The rerun on the same candidate](https://github.com/lancedb/lancedb/actions/runs/40826169185/job/123300577435) downloaded the official stable artifact and passed all 37 Java tests with zero failures/errors/skips. The release remains blocked by the separate reader issue. Pin the LanceDB 0.41 release branch to the official Lance 14.0.2 packages. Keep the frozen product baseline at `45f987a29b6c12feb2b5fc613a6593e5f636a7ce` and the newer Lance dependency on main. All 15 Rust declarations use exact crates.io versions, Python uses the official stable wheel, and Java uses the stable Maven artifact. The vendored Lance Arrow and object_store Git overrides are removed. The LSM `BitmapAsBTree` change is limited to its test adapter and retains the physical-ID and query assertions. The Lance Arrow declaration remains inherited from the workspace. Validation: - The same source against official RC1 passed all 50 relevant PR checks, including 1,977 Rust core tests and the nullable-struct regression. - Stable source commit `40f15ed1b71b66950961b175829fdf17a763f108` differs from voted RC1 only by version substitutions in eight files. - `cargo fmt --all -- --check` and `cargo clippy --profile ci --features remote --tests --examples` passed against the official crates.io packages. - Locked Cargo metadata and normalized Cargo packaging passed; 995 unrelated Cargo lock entries were retained. - Six official PyPI wheel URLs/hashes are locked. Frozen environment installation, `lance` 14.0.2 import, and Ruff format/check passed. Unrelated UV packages and resolution markers are retained. - Full CI on the stable dependency commit is required before merge. Local Python SDK tests were not run because this validation environment has no installed LanceDB native extension; those tests run in PR CI. - Java checks run in CI; no local JDK is installed. Upstream release: https://github.com/lance-format/lance/releases/tag/v14.0.2 Remote materialized-view operations now use SQL and require matching server command support; older servers can reject describe/list operations. This known compatibility issue is outside the Lance patch scope and does not block this release, as agreed by the release manager. CI compatibility: derive the Lance checkout tag from an exact registry version when no Git tag is declared, and exercise local overrides for both crates.io and Git consumers. Both RC/stable tag readers and the exact stable downstream consumer metadata probe passed locally. This changes only the workflow; the 14.0.2 dependency/product code is unchanged. Release-hook correction: the dry run exposed Maven being set to `0.41.0-final.0`. Omit bump-my-version's optional `final` marker in the Java version hook so all SDKs publish as `0.41.0`. The actual hook passed beta.0, beta.17, final.0 and absent-prerelease probes; a fresh full stable dry run verifies Maven output before publication.