lance-context 0.5.x pulls two incompatible lance majors (0.5.x needs lance 7.x, but pinned lance-graph 0.5.4 needs lance 1.x)

[dcfocus]

Summary

The 0.5.x release line of lance-context pulls two incompatible major versions of lance (and lance-namespace) into a single dependency tree, because its pinned lance-graph was not re-cut against the newer lance.

Evidence (from crates.io published metadata)

lance-context-core 0.3.0 -> 0.5.1 declare:

lance            ^7.0.0
lance-index      ^7.0.0
lance-namespace  ^7.0.0
lance-graph      ^0.5.4

but lance-graph 0.5.4 (the exact version pinned above) declares:

lance            ^1.0.0
lance-linalg     ^1.0.0
lance-namespace  ^1.0.1

So lance resolves to both ^7 and ^1 (and lance-namespace to both ^7 and ^1.0.1) in the same tree.

Why this is a problem

• Any native lance / lance-namespace type crossing the lance-context <-> lance-graph boundary won't type-check (distinct types from distinct majors).
• Even when interchange is Arrow-only, two lance runtimes touching the same datasets risk on-disk format skew across six majors.

What was coherent

The 0.2.x line was internally consistent -- lance-context-core 0.2.4 used lance ^1.0.0 and lance-graph ^0.4.0, which itself uses lance ^1.0.0.

Ask

Cut a lance-graph release built against lance 7.x (+ lance-namespace 7.x) and bump lance-context-core's lance-graph pin so the 0.5.x line resolves to a single lance major.

Related to but distinct from #153 (bump lance deps for perf). #153 is a plain version bump; this is a correctness/build problem in the lance-context 0.5.x dependency tree, and the target must be lance 7.x specifically to match what lance-context-core 0.3.0+ already declares -- bumping to any other major just relocates the mismatch.

Happy to test a pre-release. (Consumer side: Python lance-context==0.4.0 with pylance==4.0.1.)