Skip to content

Release DataFog 4.12.0 - #190

Merged
sidmohan0 merged 25 commits into
mainfrom
dev
Nov 16, 2026
Merged

sidmohan0 merged 25 commits into
mainfrom
dev

Conversation

@sidmohan0

Copy link
Copy Markdown
Contributor

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.0 minor series from #189. Existing plain-hash formats remain compatible; explicit keyed HMAC is available.

Qualified release head 3e48c34165514f6095c18dfdb9afd59153b495da was merged normally to dev as bffff506abb4106f7d684b22daa674437d65b7ba; 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.

…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
@sidmohan0
sidmohan0 merged commit 709e7eb into main Nov 16, 2026
44 of 69 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant