Skip to content

Prepare DataFog 4.12 release with Core 2 - #188

Closed
sidmohan0 wants to merge 2 commits into
fix/review-4.11-remediationfrom
release/4.12-core2
Closed

sidmohan0 wants to merge 2 commits into
fix/review-4.11-remediationfrom
release/4.12-core2

Conversation

@sidmohan0

@sidmohan0 sidmohan0 commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

Superseded by #189 — Prepare DataFog 4.12 release with Core 1.5. The approved version plan uses Core 1.5.0 and Python 4.12.0. This Core 2 draft and its artifact qualification are retained below as review history and must not be used for publication.


Prepare the dependent 4.12.0 release with datafog-core~=2.0.0 in both the base package and rust extra. Current documentation points to the reviewed Core 2 contract, and release notes explain the resulting detection fixes, preserved plain-hash defaults, explicit HMAC and the first-output latency from buffered streaming.

Stacked on #187. Merge remains blocked until Core 2.0.0 is published and this Python candidate passes installed-wheel and release qualification against the actual published Core artifacts. Keep this PR as a draft until that gate passes. This change publishes no package and creates no release tags. Source-wheel integration is additional evidence and does not replace published-artifact qualification.

Validation of candidate 43363a6581253cc7150c2aa5bbf267df78fddc5e on Python 3.12: built a fresh wheel, installed it with the local Core 2.0.0 wheel, passed pip check and python -I scripts/check_rust_install.py, then ran the complete non-slow suite against the installed package using isolated Python and pytest importlib mode: 1,138 passed, 21 skipped, 295 deselected and 19 xfailed. Optional model/OCR/Spark profiles were not provisioned for this isolated run. All applicable pre-commit hooks passed, and packaged datafog/ bytes match the committed candidate source.

Candidate artifact identities:

  • Python wheel SHA-256: 8bffc65e4613ab881dcff7b4ac337c9fd6b52ab253ebf3c9e2fb82223a98a647
  • Local source-built Core wheel SHA-256: 0d2d8fc83d1bc8a5a7b1ea8d1852c213f035b88ea9f78ad78a3eaa1d51cce09f

After #187 merges, retarget this PR to the development branch and qualify it against the published Core release before merging.

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