lance-format / lance-format/lance-c
build: repin lance to the upstream commit once lance-format/lance#9351 merges
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5
- Forks
- 14
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 18
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Wait for lance-format/lance#9351 to merge, then inspect the Lance revision pins in Cargo.toml and Cargo.lock. Replace 356acb0d with the merged upstream commit, and run cargo test to verify the dependency update still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100