Skip to content

Remove wrong changelog about default Python version in the image #36777

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
potiuk merged 1 commit into from
Jan 14, 2024
Merged

Remove wrong changelog about default Python version in the image #36777

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 0 additions & 8 deletions docs/docker-stack/changelog.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,14 +53,6 @@ Airflow 2.8
working with ``Debian Bookworm``. While all reference images of Airflow 2.8.0 are built on ``Debian Bookworm``,
it is still possible to build deprecated custom ``Debian Bullseye`` based image in 2.8.0 following the

* The "latest" image (i.e. default Airflow image when ``apache/airflow`` is used or
``apache/airflow:slim-latest``) uses now the newest supported Python version. Previously it was using
the "default" Python version which was Python 3.8 as of Airflow 2.7. With Airflow reference images
released for Airflow 2.8.0, the images are going to use Python 3.11 as this is the latest supported
version for Airflow 2.8 line. Users can use Python 3.8 by using ``apache/airflow:2.8.0-python3.8`` and
``apache/airflow:slim-2.8.0-python-3.8`` images respectively so while the change is potentially
breaking, it is very easy to switch to the previous behaviour.

* By default the images now have "MariaDB" client installed. Previous images had "MySQL" client installed.
The MariaDB client is a drop-in replacement for "MySQL" one and is compatible with MySQL. This might
be a breaking change for users who used MySQL client in their images, however those should be very
Expand Down