Graphit Code native libraries

This repository publishes immutable, verified native dependency bundles used by Graphit Code builds.

Each release contains one archive for Linux amd64, macOS arm64, and Windows amd64. Every archive has a sibling .sha256 file, an internal SHA256SUMS, and a manifest.json recording the exact LanceDB revisions and patch, LadybugDB versions, and ONNX Runtime versions.

The repository owns the minimal LanceDB binding patch and its build recipe. The release workflow applies that patch to the pinned upstream lancedb-go commit and builds on the matching GitHub-hosted operating system without checking out Graphit Code. LadybugDB, its HTTPFS extension, and ONNX Runtime are downloaded from their pinned upstream releases and verified before packaging.

The same entry point is available to maintainers as make lancedb-native PLATFORM=<platform>; make bundle PLATFORM=<platform> also assembles the verified archive.

What the LanceDB patch adds

The patch keeps the upstream Go binding unchanged and extends only its native library:

• simple_lancedb_clone_table creates a shallow clone of a table at a version or tag.
• Native Lance branches. The Go binding creates table handles only through simple_lancedb_open_table, so the branch is selected in the table name, which a LanceDB table name can never contain: <table>#branch=<name> returns a handle scoped to an existing branch, and <table>#fork=<name> checks it out or creates it from the main lineage's latest version. A losing concurrent create waits briefly for the winner's branch instead of failing. Every read and write through that handle stays on the branch.
• simple_lancedb_list_branches and simple_lancedb_delete_branch act on a table dataset by URI with storage options; force also removes a branch dataset left without metadata by an interrupted create.

Recipe versions are immutable. Updating any source, patch, dependency, or checksum requires a new NATIVE_RECIPE_VERSION.

Graphit Code pins the recipe and each platform archive digest in its own native-deps.env. Local builds and Graphit Code CI download the same release asset, verify the outer archive digest and the archive's internal checksums, then install the libraries into their existing build locations. This keeps native dependency artifacts out of Graphit Code product releases and avoids rebuilding them for every checkout or release.

Publishing an update

Update every version, source revision, and upstream checksum in native-deps.env, increment NATIVE_RECIPE_VERSION, and push the change to main. The workflow publishes a release only after all three native runner jobs build and package successfully; an existing recipe tag is never overwritten.