Skip to content

Update SlateDB fork to v0.15 - #996

Merged
xav-db merged 3 commits into
feat/static-error-codesfrom
agent/update-slatedb-v0-15
Aug 18, 2026
Merged

xav-db merged 3 commits into
feat/static-error-codesfrom
agent/update-slatedb-v0-15

Conversation

@matthewsanetra

@matthewsanetra matthewsanetra commented Aug 17, 2026 •

Copy link
Copy Markdown
Contributor

What changed

  • update the Helix SlateDB fork revision from dfe4b4dc to merge commit 30d9f28c
  • consume SlateDB v0.15.0 from the merged Port HelixDB fork changes to SlateDB v0.15 slatedb#8 port
  • refresh the workspace, migration-parity, and checked-in fuzz lockfiles
  • use a portable /tmp fallback for production-coverage scripts on Ubuntu runners

Revision provenance

SlateDB commit 30d9f28cfeb93cf95652aac2b7724811c5c49630 is the merge commit for HelixDB/slatedb#8. Its second parent is a60a1234f8b6a184381b0b0b2dc88c1cabd010f7, the former codex/port-v0.15 branch tip. Pinning the merge commit validates the merged main-branch state while retaining the exact PR revision in its ancestry.

Why

The SlateDB v0.15 fork port is now merged. Helix should validate the immutable merged revision rather than the former draft branch tip.

Impact

No Helix source compatibility changes were required beyond the existing SlateDB v0.15 migration-parity adjustments. The production-coverage script change only replaces the macOS-specific /private/tmp fallback with portable /tmp.

Validation

  • cargo fmt --all -- --check
  • cargo clippy --workspace -- -D warnings
  • cargo metadata --locked resolves SlateDB v0.15.0 at 30d9f28c
  • all four checked-in lockfiles resolve SlateDB packages at 30d9f28c
  • shell syntax and unset-TMPDIR fallback checks pass

@matthewsanetra
matthewsanetra force-pushed the agent/update-slatedb-v0-15 branch from 7454c8f to 9499e23 Compare August 18, 2026 09:10
@matthewsanetra
matthewsanetra force-pushed the agent/update-slatedb-v0-15 branch from 75daeab to 8341693 Compare August 18, 2026 10:37
@matthewsanetra
matthewsanetra changed the base branch from planner/better-contract-boundaries to feat/static-error-codes August 18, 2026 10:37
@matthewsanetra
matthewsanetra marked this pull request as ready for review August 18, 2026 10:51
Comment thread crates/db/Cargo.toml

[dependencies]
slatedb = { git = "https://github.com/HelixDB/slatedb.git", rev = "dfe4b4dc38609db8b3fe8dc6f2d3de64bfe63f0e" }
slatedb = { git = "https://github.com/HelixDB/slatedb.git", rev = "30d9f28cfeb93cf95652aac2b7724811c5c49630" }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 SlateDB revision target mismatch

When Cargo resolves this dependency, it fetches commit 30d9f28c rather than the a60a1234 revision identified by the PR, causing builds and migration-parity checks to validate a different fork state than intended.

@matthewsanetra
matthewsanetra force-pushed the agent/update-slatedb-v0-15 branch from 8341693 to edc59c1 Compare August 18, 2026 10:59
@matthewsanetra
matthewsanetra force-pushed the agent/update-slatedb-v0-15 branch from edc59c1 to 2334eb4 Compare August 18, 2026 12:22
@matthewsanetra
matthewsanetra force-pushed the agent/update-slatedb-v0-15 branch from 2334eb4 to 07d3cc0 Compare August 18, 2026 16:13
@xav-db
xav-db merged commit 429cdff into main Aug 18, 2026
44 of 69 checks passed
@xav-db
xav-db deleted the agent/update-slatedb-v0-15 branch August 26, 2026 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants