tisonkun opened a new pull request, #257: URL: https://github.com/apache/datasketches-rust/pull/257
## Summary - set the `datasketches` crate and workspace lockfile version to 0.5.0 - freeze the accumulated release notes under an undated `v0.5.0` section while keeping `Unreleased` ready for later work ## Why this PR is intentionally small This is the final release-preparation pass after the focused hardening work in #247, #253, #254, and #256. I audited the public API surface, rustdoc coverage, package contents, integration-test layout, serialization boundaries, open issues, and the history of reverted pre-release changes. The audit did not identify another behavior change with enough evidence and a sufficiently narrow contract to include safely here. In particular, this PR does not reintroduce Count-Min saturation: the earlier implementation broke signed-weight and merge semantics. A checked-overflow design would change the update and query APIs and needs a separately reviewed contract. It also does not add speculative reset methods, deep `estimated_size` accounting, repetitive feature labels, or tests that merely mirror existing coverage. As a throwaway diagnostic, deserializers for Bloom, Count-Min, CPC, Frequencies, HLL, REQ, and T-Digest were exercised against truncation and single-byte mutation without finding a panic. That diagnostic was deliberately not retained as another broad, low-signal test. ## Commit structure Each release action is independently reviewable: 1. `build: set the datasketches version to 0.5.0` 2. `docs(changelog): finalize the 0.5.0 release notes` ## Validation - `cargo x prepare-testdata` - `cargo x check` - `cargo x test` - `cargo x lint` - `cargo package --package datasketches --list --locked` - `cargo publish --dry-run --locked --package datasketches` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
