oakvcs-core 0.114.0

Core version-control primitives for Oak: BLAKE3 content hashing, content-defined chunking, diff/merge, the Blob/Manifest/Commit/Tree data model, and the client-side local repository (SQLite + git backends).
Documentation

oak-core

Core version-control primitives for Oak.

oak-core is the shared foundation used by both the Oak CLI and the Oak server. It is free of network and server concerns so the same content model and hashing rules are used on both sides of a push/pull. Its only storage is the optional client-side local repository (the default local-repo feature: SQLite and git backends), which the server leaves off.

What's in here

  • Content hashing — BLAKE3-based, content-addressed object IDs.
  • Content-defined chunking — fastcdc-based splitting for efficient large-file storage and deduplication.
  • Data model — Blob, Manifest, Commit, Tree, Branch, Tag, and the related wire types that travel between client and server.
  • Diff & merge — line-level diffing and 3-way merge helpers.
  • Ignore handling — .gitignore/.ignore-style pattern matching.

Because these types define both the on-disk hashes and the sync wire format, the CLI and server must build against the same oak-core — that is exactly why it lives in its own crate.

Usage

Published on crates.io as oakvcs-core (the oak-core name was taken), but the library is imported as oak_core:

[dependencies]
oakvcs-core = "0.114.0"
use oak_core::{Blob, Manifest, Commit};

Server-side consumers that only need the data model can skip the local SQLite/git layer:

[dependencies]
oakvcs-core = { version = "0.114.0", default-features = false }

License

Licensed under the Apache License, Version 2.0.