lance-duckdb: Skill for Claude Code

lance-duckdb Update Lance Dependency

Scope

Use this skill in the lance-format/lance-duckdb repository when updating Lance Rust dependencies to a specific Lance version or tag.

Inputs can be a version (7.2.0-beta.1), a tag (v7.2.0-beta.1), a tag ref (refs/tags/v7.2.0-beta.1), or latest.

Workflow

1. Confirm the worktree status with git status --short.

2. Resolve the target Lance version:

   • If the input is latest, empty, or omitted, run:

     python3 ci/check_lance_release.py
     

     Parse the JSON output. If needs_update is not true, stop without creating a PR. Otherwise use latest_tag.

   • If the input is explicit, use it directly.

3. Compute update metadata without changing files:

   python3 ci/update_lance_dependency.py "$TAG_OR_VERSION" --metadata-only
   

   Before making changes, check for an existing open PR with the emitted pr_title:

   gh pr list --search "\"$PR_TITLE\" in:title" --state open --limit 1 --json number,url,title
   

   If a matching open PR exists, stop and report it instead of creating a duplicate.

4. Run the deterministic update entrypoint:

   python3 ci/update_lance_dependency.py "$TAG_OR_VERSION"
   

   This updates the direct Lance Rust crate versions in Cargo.toml, removes repository-local Lance [patch.crates-io] entries if present, refreshes Cargo.lock with precise Cargo updates, and prints JSON metadata containing branch_name, commit_message, and pr_title.

5. Run validation:

   cargo fmt --all
   cargo check --manifest-path Cargo.toml
   cargo clippy --manifest-path Cargo.toml --all-targets
   

   If Cargo reports incompatible Arrow/DataFusion requirements, inspect the target Lance release requirements and update the pinned Arrow/DataFusion versions in Cargo.toml, then rerun python3 ci/update_lance_dependency.py "$TAG_OR_VERSION" and the validation commands. Fix real diagnostics and rerun validation until it succeeds.