chore(deps): upgrade slatedb to 0.15.0 - #671
Conversation
Co-Authored-By: Shikhar Bhushan <shikhar@s2.dev>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Greptile SummaryUpgrade SlateDB from 0.14.1 to 0.15.0.
Confidence Score: 5/5The PR appears safe to merge, with no concrete changed-code defects identified. The manifest and lockfile consistently resolve SlateDB at 0.15.0, and the changed dependency graph does not establish a reachable build, runtime, or security failure. Important Files Changed
Reviews (1): Last reviewed commit: "chore(deps): upgrade slatedb to 0.15.0" | Re-trigger Greptile |
|
Devin, can you please report on what's changed upstream. Double check nothing of consequence for our usage. |
|
Upstream report, v0.14.1 → v0.15.0 (74 commits, compare): Relevant to our usage (behavioral, no code changes needed):
Not relevant / opt-in only:
Compatibility: no changes to the flatbuffer manifest/SST schemas between the tags, so on-disk format is compatible; no migration needed. Our code (transactions, |
|
fix CI buddy |
Co-Authored-By: Shikhar Bhushan <shikhar@s2.dev>
|
Fixed — the |
Summary
Upgrade SlateDB
0.14.1→0.15.0(used bylite/withlz4/zstdfeatures). No API changes were required —lite/compiles unchanged; onlyCargo.tomlandCargo.lockwere updated (slatedb,slatedb-common,slatedb-txn-objall to 0.15.0).Verified:
just fmt,just clippy(-D warnings),just build,just test(713/713 passed).Link to Devin session: https://app.devin.ai/sessions/8aa009c303b14317a9a17fb7f219a700
Requested by: @shikhar