potiuk commented on PR #66061:
URL: https://github.com/apache/airflow/pull/66061#issuecomment-4475997449

   @Srujan-rai This PR has been converted to **draft** because it does not yet 
meet our [Pull Request quality 
criteria](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-quality-criteria).
   
   **Issues found:**
   - :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. 
Typically means the change uses a symbol or API not present in older Airflow 
core versions; check `airflow>=...` lower bounds and conditional imports in the 
affected provider(s). See the [provider distributions 
docs](https://github.com/apache/airflow/blob/main/contributing-docs/12_provider_distributions.rst).
   
   **What to do next:**
   - Resolve the compat failures by guarding new APIs with version-aware 
imports or by adjusting the provider's `airflow>=…` lower bound if the change 
really requires the newer core.
   - Mark the PR as "Ready for review" when you're done.
   
   Converting a PR to draft is **not** a rejection — it is an invitation to 
bring the PR up to the project's standards so that maintainer review time is 
spent productively. 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]

Reply via email to