potiuk commented on PR #63937: URL: https://github.com/apache/airflow/pull/63937#issuecomment-4473467184
@tardunge Converting back to **draft** — CI is still failing on the [Pull Request quality criteria](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-quality-criteria) after the un-draft. **Issues found:** - :x: **Build documentation**: `CI image checks / Build documentation (--docs-only)` and `Build documentation (--spellcheck-only)` are failing. Run `breeze build-docs` locally and fix the docs / spelling failures it surfaces. See the [docs-building docs](https://github.com/apache/airflow/blob/main/contributing-docs/11_documentation_building.rst). - :x: **Provider-distribution compat tests**: `Compat 2.11.1:P3.10`, `Compat 3.0.6:P3.10`, `Compat 3.1.8:P3.10`, and `Compat 3.2.1:P3.10` are failing. Likely the new Redis async hook code uses a symbol not present in older Airflow core versions; check the provider's `airflow>=…` lower bound and conditional imports. See the [provider distributions docs](https://github.com/apache/airflow/blob/main/contributing-docs/12_provider_distributions.rst). - :warning: **Earlier review threads**: the seven Copilot review threads from 2026-04-02 are still showing as unresolved — please click "Resolve conversation" on the ones you've addressed (mentioned in our [earlier follow-up](https://github.com/apache/airflow/pull/63937#issuecomment-2820019015)). **What to do next:** - Fix the documentation / spellcheck failures: `breeze build-docs`. - Resolve the compat failures (version-aware imports or provider `airflow>=…` adjustment). - Click "Resolve conversation" on each Copilot thread you've addressed. - Mark the PR as "Ready for review" when all of the above is done. Converting a PR back to draft is **not** a rejection — it just keeps the review queue accurate so that maintainer time is spent where it matters. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the [Airflow Slack](https://s.apache.org/airflow-slack). --- _Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this [two-stage triage process](https://github.com/apache/airflow/blob/main/contributing-docs/25_maintainer_pr_triage.md#why-the-first-pass-is-automated) so that our maintainers' limited time is spent where it matters most: the conversation with you._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
