potiuk commented on issue #17301:
URL: https://github.com/apache/airflow/issues/17301#issuecomment-888817398


   It is only really needed when you want to force-update some dependency and 
increase the minimum version (like we did with FAB) - in all other cases it 
will work just fine and Breeze will automatically upgrade to latest constraints.
   
   I will thin maybe how to avoid this in the future. I think what might 
actually help is that in this case I could fall-back to non-constraint 
installation just to get things going. Let me think about all the cases and I 
will implement something. For sure it could be helpful for PRs and locally 
building Breeze but should be disabled when you try to build production image 
(and fail hard in this case as it would indicate a real conflict).


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