Repository navigation
chore: release 0.4.0 - #9
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E3AAifuwHuKGdoVpqZoQAo
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.
Bumps the version to 0.4.0 in
package.jsonandpackage-lock.json. No code changes.After merge, the tag
v0.4.0on the merge commit triggers the publish job in CI.What 0.4.0 contains (since 0.3.0)
scrub()now also redacts German street addresses (street word + 1–3 digit house number) and PII inside URLs: components are decoded and scrubbed, and map links lose the place name and place ids, with coordinates rounded to 2 decimals. IBANs are mod-97 checked. Classification fixes forinternal_user, curated_titledefaults, anddata_classification: 'pii'.Why a minor version
#6 changes what
scrub()redacts: text that 0.3.0 left unchanged can come out redacted. For a 0.x package,^0.3.0accepts any 0.3.x automatically, so a patch release would reach consumers on^0.3.0without them opting in. 0.4.0 needs an explicit bump.Checks
v0.4.0on the merge commit, publish job succeedsreturns0.4.0`Generated by Claude Code