mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
56 lines
2.2 KiB
TOML
56 lines
2.2 KiB
TOML
[package]
|
|
name = "deltalite-core"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
# CI compiles with this exact toolchain; cargo's MSRV-aware resolver uses it to
|
|
# avoid picking dependency versions CI cannot build (aws-* crates move MSRV often).
|
|
rust-version = "1.91.1"
|
|
publish = false
|
|
|
|
[lib]
|
|
name = "deltalite_core"
|
|
|
|
[lints]
|
|
workspace = true
|
|
|
|
[dependencies]
|
|
# VERSION SKEW WITH THE PYTHON `deltalake` PACKAGE IS DELIBERATE.
|
|
#
|
|
# The delta-rs tree behind Python `deltalake==1.6.1` (pinned in the repo's
|
|
# pyproject.toml) is the in-repo crate version 1.0.0 at git tag `python-v1.6.1`.
|
|
# That tag is NOT buildable as published: it pins its delta kernel dependency to
|
|
# a MOVING BRANCH (`buoyant/main`) rather than a rev, delta-rs gitignores its
|
|
# Cargo.lock so nothing records the rev the wheel was built from, and the branch
|
|
# has since diverged in two mutually incompatible directions (package rename vs
|
|
# removed feature), so no reachable revision satisfies the tag's requirements.
|
|
#
|
|
# We therefore pin the newest PUBLISHED crates.io release exactly and commit the
|
|
# lockfile. Both writers emit the same Delta protocol; the Python differential
|
|
# parity suite (rust/deltalite/python/tests/) -- not version equality -- is the
|
|
# real compatibility check, and every bump of either side must keep it green.
|
|
#
|
|
# Built WITHOUT the `datafusion` feature: no DataFusion in the dependency tree
|
|
# means the delta-io/delta-rs#4614 merge deadlock is impossible by construction.
|
|
deltalake = { version = "=0.32.4", default-features = false, features = ["s3", "rustls"] }
|
|
|
|
# arrow/parquet major version must match what `deltalake` links (arrow 58).
|
|
arrow-array = { version = "58" }
|
|
arrow-buffer = { version = "58" }
|
|
arrow-cast = { version = "58" }
|
|
arrow-data = { version = "58" }
|
|
arrow-row = { version = "58" }
|
|
arrow-schema = { version = "58" }
|
|
arrow-select = { version = "58" }
|
|
parquet = { version = "58", features = ["async", "object_store"] }
|
|
object_store = { version = "0.13.2" }
|
|
|
|
async-trait = { workspace = true }
|
|
bytes = { workspace = true }
|
|
futures = { workspace = true }
|
|
metrics = { workspace = true }
|
|
serde_json = { workspace = true }
|
|
thiserror = { workspace = true }
|
|
tokio = { workspace = true }
|
|
tracing = { workspace = true }
|
|
uuid = { workspace = true }
|