Repository navigation
Establish Core 0.4 capabilities and compatibility release gates - #31
Merged
Merged
Conversation
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.
Core consumers currently need their own entity inventories and cannot discover locale or UUID activation. Add Rust registry-backed capabilities() in Rust and Python, fresh typed capability data, strict locale validation, and runtime activation/offset compatibility gates. Structured-only PERSON is explicitly scoped.
Align package versions to 0.4.0 and document the 0.4.x compatibility policy, activation inventory, migration behavior, and publication gate in Mintlify. This PR is stacked on the NPI PR and will target main after its predecessors merge.
Validation: Rust fmt, strict workspace Clippy, all-feature tests; installed Python wheel and isolated sdist rebuild contract/typing tests; installed Node and browser WASM package suites; Mintlify validation and anchor checks. Python adapter integration against the exact candidate wheel passes locally: 352 focused checks, 833 base/CLI checks, installed-wheel smoke and dependency checks. Follow-up draft: DataFog/datafog-python#179. Hosted CI and published-artifact validation remain outstanding. No tag or publication is authorized.
Intentional behavior change: unsupported explicit locales now raise the existing configuration exception; de/de-DE/de_DE enable German detectors, while en-US/fr remain accepted base-only compatibility aliases.
Candidate artifact:
datafog_core-0.4.0-cp310-abi3-macosx_11_0_arm64.whl, SHA256351ab81ae575b31a6739a43e29135884ccc0d7152f01df568cd1f7608d690b1c. Built from source60c4636; this PR head has the identical source tree, reparented onto the focused detector stack. Python validation used macOS ARM64 and CPython 3.12; this is not a claim of cross-platform coverage.Reviewed compatibility limitation: legacy Python overlap-before-selection can keep PHONE over same-span NPI, so selecting NPI may produce no legacy finding. Native Core/datafog.v5 scanning preserves both, and native transformations can select NPI. Existing Python priorities/filtering order are preserved and regression-tested.