Skip to content

Fix failing static checks by regenerating breeze command output#70287

Merged
shahar1 merged 1 commit into
apache:mainfrom
shahar1:regenerate-breeze-release-management-output
Jul 23, 2026
Merged

Fix failing static checks by regenerating breeze command output#70287
shahar1 merged 1 commit into
apache:mainfrom
shahar1:regenerate-breeze-release-management-output

Conversation

@shahar1

@shahar1 shahar1 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

update-breeze-cmd-output currently fails on main, so every branch cut from it inherits a red static-check job.

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. This regenerates the 10 affected files; the only content change is that provider dropping out of the choice lists.

related: #70275


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 4.8, 1M context)

Generated-by: Claude Code (Opus 4.8, 1M context) following the guidelines

Marking the Common Data Quality provider as not-ready (apache#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.
@shahar1
shahar1 merged commit 8c48675 into apache:main Jul 23, 2026
64 checks passed
@shahar1
shahar1 deleted the regenerate-breeze-release-management-output branch July 23, 2026 09:05
@github-actions

Copy link
Copy Markdown
Contributor

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-3-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 8c48675 v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants