potiuk commented on PR #36143: URL: https://github.com/apache/airflow/pull/36143#issuecomment-1848603934
> Then How did this ever worked? It's a very recent change when I split installation to two (last week), and it worked fine as long as you have not added a limit that violated the "previous" constraints. Simply we did not have a case like that since last week (it's pretty rare). In this case constraints in https://github.com/apache/airflow/blob/constraints-main/constraints-3.8.txt (as of now) have google-cloud-automl==2.11.4 - but what my PR (#36141) does, it adds `google-cloud-automl>=2.12.0` as requirement for Google provider. I have to do it, because older libraries had wrong type specification for some automl methods (Retry instead of AsyncRetry) - so really the best way is to also bump the min version while we are fixing type in our Hooks and Operators (they are passing retry directly to the library). So we have now confllct: * old-constraints = 2.11.4 * requirements in the incoming PR: >=2.12.0 This is why #36141 is failing currently. The thing is that the CI image of ours used in this PR is already built with `--upgrade-to-newer-dependencies` - which means that NEW constraints after this build succeed will have 2.12.0 already. So this change basically boils down to: > let's use the new constraints that this PR generated to install the new providers built in this PR. -- 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]
