Re: [PR] Replace chicken-egg providers with automated use of unreleased packages [airflow]

Fri, 25 Apr 2025 17:02:48 -0700 


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

   Some more checks:
   
   1) when generating PyPI constraints we automatically build the 
non-released-yet providers  (either being voted or not yet even RC-d)
   
   
![image](https://github.com/user-attachments/assets/b2f9b9ad-dd89-415e-abb0-9625a9190413)
   
   2) they are nicely reflected in PYPI constraints:
   
   
![image](https://github.com/user-attachments/assets/f837823a-e530-46f7-ac50-eb44374001ba)
   
   3) When building PROD image for testing in CI. all "prod" prod packages are 
built from sources - and the non-released yetproviders have the "future" 
versions:
   
   
![image](https://github.com/user-attachments/assets/29c515b7-d693-4d16-8ff1-7cbfff22d4de)
   
   4) This all works despite `common.compat 1.6.1` not released yet 
   
   
![image](https://github.com/user-attachments/assets/636099d6-5cb8-4d01-a0da-52a4aff2a0a5)
   
   5) And with several packages having common.compat >= 1.6.1 in their 
dependencies:
   
   
![image](https://github.com/user-attachments/assets/e7ead8cc-c684-4b0c-bfe4-87a6f9a29c39)
   
   
   All seem to be working as expected.
   
   
   


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