potiuk commented on issue #36187: URL: https://github.com/apache/airflow/issues/36187#issuecomment-1852905056
> We should indeed test, but should we not yank the older released providers? This seems over doing the backwards compat (and maintaining it!) While the feature , somewhat arguably, couldn't be used. This would not work. Yanking is when there is an error, and we already have some of those providers as part of "golden" constraints in some versions of airflow, which means that when someone upgrades just airflow without providers, they will still remain with those versions. Yanking only prevents people from making specific version available for `pip` resolver when it resolves new set of packages to install, but when you either specified the version explicitly (which we do with constraints) or when the package is already installed `yanking` has no effect. So in scenario when someone installed `airflow[amazon]==2.7.3` and after that `airflow==2.8.0` they would end up with broken amazon provider. -- 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
