Repository navigation
Conversation
…4.12-core1.5 # Conflicts: # README.md # docs/review-remediation.md
Fix the 4.11 review findings across detection, guardrails and releases
Release DataFog 4.12 with qualified published Core 1.5
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.
Promote the qualified DataFog 4.12.0 release from dev to main. This release carries the reviewed structured-detection, NER-offset, guardrail, CLI and packaging fixes from #187 and requires the published
datafog-core~=1.5.0minor series from #189. Existing plain-hash formats remain compatible; explicit keyed HMAC is available.Qualified release head
3e48c34165514f6095c18dfdb9afd59153b495dawas merged normally to dev asbffff506abb4106f7d684b22daa674437d65b7ba; their trees are identical. All 31 PR CI jobs, benchmark and CLA passed. The stable release dry run also passed all four full model/test/corpus gates, Python3.14 core, all four native bridges and artifact validation without publishing.The actual published Core1.5 macOS ARM wheel was independently downloaded and verified, then tested with the installed Python candidate: 1,143 passed, 21 skipped, 19 expected failures; pip check and isolated native smoke passed. All published Core runtime bytes match the exact build with 726-pass real-model/native contract evidence. A fresh clean3.12 install resolves the published dependency and passes native integration.
After this PR passes checks and merges normally, the existing release workflow will run against frozen main with stable
version_override=4.12.0, retaining all test gates before the explicitly owner-authorized PyPI upload and immutable v4.12.0 tag. The published wheel and sdist will be checked against retained workflow artifacts, installed cleanly, and main/dev/tag synchronization verified.