Release v0.5.0#56
Merged
Merged
Conversation
Bump crate and dumpling-cli package versions; fold Unreleased changelog into 0.5.0 with compare link. Includes first-class PII strategies, faker/RNG optimizations, and SQL streaming performance improvements. Co-authored-by: Andy Babic <ababic@users.noreply.github.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
2 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.
Release v0.5.0
Version bump for Rust crate (
Cargo.toml/Cargo.lock) and Python packagedumpling-cli(pyproject.toml).CHANGELOG.mdmoves the previous [Unreleased] notes into [0.5.0] and restores an empty Unreleased section. Docs:docs/src/releasing.mdchecklist now mentionspyproject.toml.Semver rationale (0.5.0 vs 0.4.4)
0.5.0 is appropriate because:
email/name/first_name/last_namestay as those strategy names after load instead of being rewritten tofaker, which can break tools or tests that introspectedResolvedConfig.faker/phone/ PII now share oneStdRngon the registry; two back-to-back anonymizations that used to each re-seed can produce a different sequence than before for the same--seed(domain-mapped and deterministic paths are unchanged in intent).Patch-only 0.4.4 would understate those behavioral/config-surface changes.
After merge
From
mainafter this PR lands:git tag -a v0.5.0 -m "Release v0.5.0" git push origin v0.5.0Then confirm the Release / Publish workflow as in
docs/src/releasing.md.Checks
cargo test --all-targets --all-featurescargo clippy --all-targets --all-featurescargo fmt --all -- --checkSlack Thread