release: prepare DataFog Python 4.9.0 - #180
Merged
Merged
Conversation
release: DataFog 4.8.1 Python 3.14 compatibility
|
|
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
3 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.
Prepare DataFog Python 4.9.0 for the authorized stable publication. Reconcile the previous stable release history into dev, set the package and bump configuration to 4.9.0, and finalize release notes and migration documentation.
The release workflow now tests a single immutable source commit, gates publication on native installed-wheel integration across Linux/macOS/Windows, preserves pytest failure exit codes, validates the final wheel and distribution metadata, and saves artifacts for review. A candidate ref is accepted only for a dry run. Real stable publication remains restricted to main and aborts if the branch advances during testing. Stable notes use the curated versioned release notes.
Python remains the default; Core support is opt-in. Notes explicitly cover deprecations and overlap-before-selection limitations, including pinning Core for reproducible detector behavior.
Local validation: 4.9.0 wheel and sdist built; twine check passed; installed 4.9.0 wheel smoke and version checks passed against published Core 0.4.0; workflow actionlint/shellcheck and ref-resolution checks passed; Sphinx build passed with existing warnings. Hosted candidate dry run and CI are required before promotion to main and publishing.