chore: prepare the 0.5.0 release - #257
Merged
Merged
Conversation
The release process requires the final package version to be present in the reviewed release commit before an RC tag is created. Update both the manifest and locked workspace package entry so package and publish checks validate the exact 0.5.0 artifact.
The release notes are still accumulated under Unreleased. Create the undated 0.5.0 section required before RC creation while preserving Unreleased for post-release work; the release date remains intentionally deferred until the release is approved.
tisonkun
marked this pull request as ready for review
September 1, 2026 01:22
tisonkun
requested review from
PsiACE,
ariesdevil and
notfilippo
and removed request for
PsiACE,
ariesdevil and
notfilippo
September 1, 2026 01:27
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.
Summary
datasketchescrate and workspace lockfile version to 0.5.0v0.5.0section while keepingUnreleasedready for later workWhy 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_sizeaccounting, 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:
build: set the datasketches version to 0.5.0docs(changelog): finalize the 0.5.0 release notesValidation
cargo x prepare-testdatacargo x checkcargo x testcargo x lintcargo package --package datasketches --list --lockedcargo publish --dry-run --locked --package datasketches