Bump redb 4.0 → 4.1.0#255
Merged
Merged
Conversation
Refresh the workspace pin to the latest 4.x release. Minor bump within the existing major; no API or on-disk format changes for the axum adapter's KV store. Closes #254
prk-Jr
approved these changes
Apr 26, 2026
ChristianPavilonis
approved these changes
May 4, 2026
aram356
added a commit
that referenced
this pull request
Jun 11, 2026
…ync) into feature/extensible-cli Pulls in two new commits on chore/strict-clippy since the last sync at 453a44b: - dbb7fa3 Bump redb 4.0 → 4.1.0 (#255) — minor bump within the existing 4.x major. No API or on-disk format changes for the axum adapter's KV store; the workspace lock already resolved HEAD's `redb = "4.1"` to 4.1.0, so the merged Cargo.lock is unchanged in practice. - c666132 Merge remote-tracking branch 'origin/main' into chore/strict-clippy — the main-into-branch sync carrying #255. Conflicts resolved in two files: - Cargo.toml: HEAD's `redb = "4.1"` vs. upstream's `redb = "4.1.0"` are semver-equivalent — kept upstream's more specific pin to track the explicit dependency intent from #255. HEAD's reqwest feature set (`["rustls", "blocking", "json"]`) is kept verbatim: upstream's set (`["rustls"]`) is from before this branch added the `blocking` + `json` features that `edgezero-adapter-fastly`'s CLI shell-out path depends on. HEAD's `rusqlite` block (introduced for the Spin local KV writer's vendored schema) is preserved — upstream didn't have it because the redb bump landed before that work merged. - Cargo.lock: 15 conflict regions. Took HEAD's lock entirely (`git checkout --ours`) — HEAD's lock already pins `redb = "4.1.0"` because `4.1` resolves to the same version, so no manual conflict surgery was needed. Verified via `cargo update -p redb` (zero packages updated, no drift). Verified on the merged tree (all gates green): - cargo fmt --all -- --check - cargo clippy --workspace --all-targets --all-features -- -D warnings - cargo test --workspace --all-targets - cd examples/app-demo && cargo test --workspace --all-targets
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
redbpin from4.0to4.1.0to track the latest 4.x release.crates/edgezero-adapter-axum/src/key_value_store.rs).Cargo.lockis refreshed (transitive deps re-resolved during the verification run).Changes
Cargo.tomlredb = "4.0"→redb = "4.1.0"Cargo.lockredb 4.0.0→4.1.0, plus incidental transitive refresh fromcargo check --all-featuresCloses
Closes #254
Test plan
cargo fmt --all -- --checkcargo clippy --workspace --all-targets --all-features -- -D warningscargo test --workspace --all-targets— full suite green (axum adapter: 102 tests passed, includingredb-backed KV contract tests)cargo check --workspace --all-targets --features "fastly cloudflare spin"cargo check -p edgezero-adapter-spin --target wasm32-wasip1 --features spinCompatibility notes
redb4.1.0 declares MSRV1.89— well below the project's pinned1.91.1.Legacy-type removal that landed in 4.0 (and which the codebase doesn't use) are unaffected.spin-sdk5.2 → 6.0 was considered alongside this but deferred — it requires rustc1.93and is being tracked separately as a toolchain decision.Checklist