Release v0.6.5 — validation & hardening - #26
Merged
Merged
Conversation
- move keywords/categories into [package] (were under docs.rs metadata, so the crate published with none); drop the inaccurate lock-free keyword - CHANGELOG: note the AccessBuffer drain as the one behavioural change rather than claiming no logic changes - soften overstated "lock-free reads" claims to the spinlock-free-metadata truth — slab-mode reads (every u64 key) still take the slab pool lock
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
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 the v0.6.5 release. The hardening work itself (fuzz #13, soak #14, Miri #16, shadow-map #18, loom #19, embedded matrix #20, QEMU #21, footprint #22, AccessBuffer drain #24) already landed on
main; this is the release-prep commit on top.Changes
keywords/categories/readmefrom[package.metadata.docs.rs]into[package]. They were misplaced, so the crate published to crates.io with zero keywords/categories. Dropped the inaccuratelock-freekeyword.[0.6.5]heading (2026-09-28) and note theAccessBufferdrain as the one behavioural change, instead of claiming "no logic changes in src/".u64key) still take the slab pool lock. Left the genuinely-accurate lock-free mentions (AccessBuffer ring buffer, MetaWord atomic loads) and the historical v0.6.2 changelog entry untouched.Pre-flight (all green on this branch)
cargo test --all-features— 58 + 11 doc tests, 0 failedcargo build --no-default-features(no_std) — cleancargo +nightly miri test -p pulse_map --lib— 55 passed, 0 failed, 3 ignored (oversized)cargo publish --dry-run— 70 files packaged, verify build OKTag
v0.6.5andcargo publishfollow after this merges tomain.