n-badtke-cg opened a new issue, #69603:
URL: https://github.com/apache/airflow/issues/69603

   ### Under which category would you file this issue?
   
   Airflow Core
   
   ### Apache Airflow version
   
   3.3.0
   
   ### What happened and how to reproduce it?
   
   The contstraints for Airflow 3.3.0 and python 3.11 
(https://github.com/apache/airflow/blob/constraints-3-3/constraints-3.11.txt#L128)
 and 3.12 
(https://github.com/apache/airflow/blob/constraints-3-3/constraints-3.12.txt#L128)
 are not properly managed, at least for the databricks provider.
   
   There is listed `apache-airflow-providers-databricks==6.13.0` which is a 
version from October 2024.
   
   `apache-airflow-providers-databricks==6.13.0` has import errors for 3.3.0
   
   With Airflow 3.2.x python 3.12 constraints 
(https://github.com/apache/airflow/blob/constraints-3-2/constraints-3.12.txt#L128),
 there is `apache-airflow-providers-databricks==7.15.0`
   
   ### What you think should happen instead?
   
   I think there should be something near the latest version 7.17. I don't know 
if this intended or if there might be a deeper issue because with Airflow 
3.2.x, a proper version is included.
   
   ### Operating System
   
   container
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Apache Airflow Provider(s)
   
   databricks
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-databricks==6.13.0
   
   ### Official Helm Chart version
   
   1.22.0 (latest released)
   
   ### Kubernetes Version
   
   1.35
   
   ### Helm Chart configuration
   
   airflowVersion: 3.3.0
   images:
     airflow:
       tag: 3.3.0
   
   ### Docker Image customizations
   
   not applicable
   
   ### Anything else?
   
   -
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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