Background
#84 (merged) bumped the pinned Lance revision from ab6b5bbe (v11.0.0) to 356acb0d333c96e970f6f84b97314fc5bc4193f7 to pick up the vector segment compatibility validation fix. That commit currently exists only on the PR branch of lance-format/lance#9351 — it is fetchable from the upstream repo URL via GitHub's object network, so builds work, but it is not a commit on any upstream branch and could become unreachable if the PR is squashed or the fork branch is deleted.
Task
Once lance-format/lance#9351 merges upstream, open a small lance-c PR that moves the rev pins in Cargo.toml (and Cargo.lock) from 356acb0d to the merged upstream commit, and verify cargo test still passes.
If #9351 is merged as a squash/rebase, the pinned SHA becomes orphaned; until then there is no urgency.
Background
#84 (merged) bumped the pinned Lance revision from
ab6b5bbe(v11.0.0) to356acb0d333c96e970f6f84b97314fc5bc4193f7to pick up the vector segment compatibility validation fix. That commit currently exists only on the PR branch of lance-format/lance#9351 — it is fetchable from the upstream repo URL via GitHub's object network, so builds work, but it is not a commit on any upstream branch and could become unreachable if the PR is squashed or the fork branch is deleted.Task
Once lance-format/lance#9351 merges upstream, open a small lance-c PR that moves the
revpins inCargo.toml(andCargo.lock) from356acb0dto the merged upstream commit, and verifycargo teststill passes.If #9351 is merged as a squash/rebase, the pinned SHA becomes orphaned; until then there is no urgency.