The GitHub Actions job "Tests" on airflow.git has succeeded.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
f419190e7fe6a92f2056ea8e7a94b76407ef436f / raphaelauv <[email protected]>
Switch our base image to use Debian bookworm

Debian bookworm (12) is the current stable version of Debian and
it is on the market for more than a year so all the other
dependencies should have enough time to catch up.

While Debian bullseye is still supported (oldstable) it will
be switching to LTS support mode (managed by volunteers) roughly in
July 2024 - but we want to switch our reference images
to bookworm long before that date.

This PR switches our reference images to Debian Bookworm for
Dockerfiles and images that will be released to Airflow 2.8.0.

Similarly as with "Debian buster -> Debian bullseye" switch we
will switch our reference images to bookworm and we will not be
publishing images based on bullseye. However our users will still
be able to build custom images using our Dockerfiles with bullseye base
image until we release Airflow 2.9.0 where the bullseye support will
be dropped entirely.

We provide release notes and instructions on how users can build
the bullseye images if they still want to do it - for example
because their system level dependencies will require them to do so,
but the users are advised to switch to bookworm-based images as soon
as possible.

The users will likely still be able to build custom Airflow images for
future airflow releases (using Dockerfiles released with Airlfow 2.8),
however as of Airflow 2.9, we will not release Dockerfiles with support
for that and we will not verify if Airflow with default depenencies can
be installed on bullseye Debian.

Co-authored-by: Jarek Potiuk <[email protected]>
Co-authored-by: raphaelauv <[email protected]>

Report URL: https://github.com/apache/airflow/actions/runs/6763114786

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to