release: v0.4.8 — production-hardening pass#90
Merged
Merged
Conversation
Bumps workspace + inter-crate pins 0.4.7 → 0.4.8, moves CHANGELOG [Unreleased] → [0.4.8], updates SECURITY.md supported-versions and the user-facing version pins (cargo install, ghcr image tags, REPL banners). Historical 'since 0.4.7' notes left intact. Ships the gold-standard hardening from #89: full RBAC lattice enforcement (behavior-preserving), resource-limit errors surfaced to remote clients, automated post-publish durability gate, MSRV build job, scoped cargo-audit, crash-only panic documentation, dead-code removal. Verified: build/clippy/fmt clean, full workspace tests 41 suites 0 failures, backward-compat (v0.4.7-created DB + auth.json open cleanly on 0.4.8, both directions), smoke-release ALL-PASS. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Cuts v0.4.8, shipping the gold-standard production-hardening pass (#89) to crates.io.
What's in it
scripts/smoke-release.sh, wired intorelease.yml) — install → PowQL flow →kill -9→ restart → assert WAL replay. The gate whose absence yanked v0.4.1–0.4.3.cargo audit, TS-version CI assert, Dockerfile dep-cache fix.panic = "abort"documented as deliberate crash-only design; every deploy example confirmed under auto-restart.[workspace.lints], removed ~190 LOC deadmvcc.rs/tx.rs, stale-doc + CLI--helpfixes.Backward compatibility — verified
A database (heap/catalog/WAL/index/unique) and
auth.jsoncreated by the published v0.4.7 binary open cleanly on v0.4.8: all rows present, unique + index intact, both named users authenticate, RBAC behaves correctly. Reverse direction (v0.4.8-created DB on v0.4.7) also works — no on-disk format bump.auth.jsonstores roles by name, soreadwritegainingDdlneeds no migration.Verification
cargo build/clippy/fmtclean · full workspace tests 41 suites, 0 failures ·scripts/smoke-release.shALL-PASS · cross-version compat ALL-PASS ·cargo auditclean · version banner0.4.8.🤖 Generated with Claude Code
Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.