patricker commented on issue #31823: URL: https://github.com/apache/airflow/issues/31823#issuecomment-1588109064
@potiuk , Sorry, a slight miscommunication on my part, let me expand on my earlier statements. First, the emphasis I was trying to make was not on "repeatable installation", but on "known-to-be-working". Yes, I want a repeatable installation, but I also know that lots of people put time and effort into testing each release, and I don't want to just switch up package versions and possibly introduce issues when there is a "known-to-be-working" version readily available. To clarify our install process of updated providers: occasionally new versions of providers are released _before_ a new version of Airflow is released. In these instances we sometimes need a bug fix that is in that new provider version (such as in this case where we have Airflow 2.6.1, but the updated provider is already available). Our assumption has been that if a new version of Airflow has not been released yet, that we should be able to update the version number on the affected provider inside our local copy of the constraints file (we keep a local copy for just this use case), especially if it's a minor version like this, without issue. When we install an updated version of a provider we don't run `pip install apache-airflow-providers-google=...` at all. We update the version number in our local copy of the constraints file, and then setup our Python env with this new constraints file. We only assume that there won't be a version issue if there has not been a new version of Airflow released. -- 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]
