Hello everyone, I have a small announcement about changes to the reference container images for 2.11.1: I re-tagged the constraints and rebuilt the reference images today for 2.11.1.
If you have already installed version 2.11 (with constraints) or you used one of our reference images, you will likely need to reinstall airflow/re-pull the images. We were a bit unlucky when we prepared 2.11.1 release because when we created the constraints, virtualenv had version 20.37.0 released - but when we released it - the version was gone - because it was (somewhat accidentally) deleted by virtualenv release manager [1] [2]. This isn't usual; typically, even bad releases are yanked. This time our constraints simply stopped working, which is why we had to re-tag constraints and re-push images as described in [3]. This was captured in the docker container changelog [4]. I also opened a PR that should prevent similar issues in the future [5]. Also I think virtualenv team learned that even brief broken release (it was ok, it was just sdist-only release) should not be removed from PyPI. J. [1] Our issue regarding the disappearing 20.37.0 virtualenv https://github.com/pypa/virtualenv/issues/3061 [2] Another issue regarding the disappearing 20.37.0 virtualenv https://github.com/pypa/virtualenv/issues/3055 [3] Reasons why we re-tag constraints and re-push images: https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#fixing-constraints-at-release-time [4] Table showing all "after the release" changes in the images: https://airflow.apache.org/docs/docker-stack/changelog.html#changes-after-publishing-the-images [5] PR to fail image publishing when constraints are broken: https://github.com/apache/airflow/pull/62387
