Conversation
docs: add CLA Assistant contributor flow
Establish the published 4.8.1 Python text API contract
Add the 4.9 Rust detection and API migration bridge
feat: discover Rust entity capabilities in the Python adapter
release: prepare DataFog Python 4.9.0
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
2 participants
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.
Release DataFog Python 4.9.0 from dev to main. This adds the opt-in Rust detection backend, capability-driven entity support, the
datafog.compat.v4namespace, and the nativedatafog.v5preview while retaining the Python default. Legacy detect/process, OCR, and Spark are deprecated for removal in 5.0.Includes the curated 4.9.0 release notes and guarded publishing workflow. Core remains optional (
datafog[rust]); native label selection is documented for overlapping findings that the legacy adapter suppresses before filtering.Validation: the merged dev tree exactly matches the release candidate. The candidate stable dry run passed Python 3.10–3.12 release tests and detection accuracy, Python 3.14 core tests, all four Rust integration platform jobs, wheel/sdist checks, and final-wheel installation against published Core 0.4.0. Publishing and tagging were deliberately skipped in dry-run mode. Local adapter integration against the future Core 0.4.1 candidate also passed 352 tests and the overlap audit; that candidate is not required for this release.
After merge, dispatch the stable 4.9.0 release from main and verify PyPI installation and GitHub release publication.