potiuk commented on code in PR #50774: URL: https://github.com/apache/airflow/pull/50774#discussion_r2096304091
########## providers/fab/provider.yaml: ########## @@ -35,6 +35,7 @@ source-date-epoch: 1747132761 # In such case adding >= NEW_VERSION and bumping to NEW_VERSION in a provider have # to be done in the same PR versions: + - 2.2.0 Review Comment: > The only case we must specify future version in versions is when you wish to set it as min version for another package I think that was the intention here (airflow has fab provider >=2.2.0). And we need to do it if we want defaults to work - this is a one-time (or actually continuation of the previous) cleanups and I think it's worth doing it. The problem is that currently the old provider will not get the right default value when it is moved to FAB section and Airflow 3.0.2 will install older provider version. Those are the teething problems we need to solve now I think by cleaning the configs, otherwise it might cause the problem for our users. And setting the right provider version now is the only way - I think. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
