Mark Common Data Quality provider as not-ready#70275
Merged
shahar1 merged 1 commit intoJul 23, 2026
Merged
Conversation
The provider is currently only a skeleton (apache#69795); the PR implementing its actual rules is still under discussion and unmerged, so it should not be picked up by provider release waves yet. breeze's package filter gates on 'state' and never reads 'lifecycle', so 'lifecycle: incubation' alone did not exclude it - the 2026-07-22 wave pulled it in and regenerated its README. Marking it not-ready matches ibm.mq, the other in-development provider, and keeps it out of release tooling until it is ready to publish.
1 task
eladkal
approved these changes
Jul 23, 2026
1 task
shahar1
added a commit
that referenced
this pull request
Jul 23, 2026
Marking the Common Data Quality provider as not-ready (#70275) removed common.dataquality from the provider-choice enum shared by five release-management commands, but the recorded help output was not regenerated in that PR. The update-breeze-cmd-output hook has failed on main ever since, so every branch cut from it inherits a red static-check job.
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.
common.dataqualityis currently only a skeleton (added in #69795) — the PR implementing its actual rules is still under discussion and unmerged — so it should not be picked up by provider release tooling yet.It is currently
state: readywithlifecycle: incubation. breeze's package filter gates purely onstateand never readslifecycle(get_available_packagesindev/breeze/src/airflow_breeze/utils/packages.py:include_regularadmits{"ready", "pre-release"}, andnot-readyis only admitted via--include-not-ready-providers). Solifecycle: incubationdid not keep it out: the 2026-07-22 release wave (#70256) picked it up and regenerated itsREADME.rst, which is what surfaced this in review.Setting
state: not-readymatchesibm.mq, the other in-development provider, and excludes it from release waves until it is ready to publish. Flip it back toreadywhen the implementation lands.Scope check:
stateis not rendered into any provider template (PROVIDER_README_TEMPLATE/PROVIDER_INDEX_TEMPLATE), andnot-readyproviders still appear ingenerated/provider_dependencies.jsonand the rootpyproject.tomlexactly asreadyones do — so no generated files change.not-readyis a valid value inprovider.yaml.schema.json.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8, 1M context) following the guidelines