Under which category would you file this issue?
Providers
Apache Airflow version
3.3.0
What happened and how to reproduce it?
Hello i am upgrading from 3.2.2 to 3.3.0 and I just noticed that the contraint for numpy has been downgraded from 2.4.6 back to 1.26.4
Having this constraint file locally, and removing the pinning of numpy worked for us
Is there a specific reason why the pinned version has been downgraded?
What you think should happen instead?
I wouldn't have expected for a pinned version to be downgraded on a version bump.
Operating System
No response
Deployment
None
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Under which category would you file this issue?
Providers
Apache Airflow version
3.3.0
What happened and how to reproduce it?
Hello i am upgrading from 3.2.2 to 3.3.0 and I just noticed that the contraint for numpy has been downgraded from
2.4.6back to1.26.4Having this constraint file locally, and removing the pinning of
numpyworked for usIs there a specific reason why the pinned version has been downgraded?
What you think should happen instead?
I wouldn't have expected for a pinned version to be downgraded on a version bump.
Operating System
No response
Deployment
None
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct