Well... That's embarrassing.. I have found. (somewhat accidentally) that despite the #36003 has been merged and cherry-picked - it was not effective - because it only moved the timing of applying "latest" alias to "2.8.0" rather than applying "2.8.0" to "python-3.11"
That's a bit of facepalm. But It also means that somehow my original announcement was about right - we are likely to have Python 3.12 support soon in main (maybe even this week as we are waiting for google-ads library to release 3.12 compatible version) so LIKELY this change will come in Airflow 2.9 and Python 3.12 being aliased from "airflow:2.9.0" and "airlfow:latest". I am reverting the changelog about it and will apply it in main with "proper" fix shortly. J. On Fri, Dec 1, 2023 at 12:41 PM Jarek Potiuk <ja...@potiuk.com> wrote: > Small correction - it is "3.11" - we do not support 3.12 yet - mostly due > to Pendulum holding us back. > > The PR switching it is here: https://github.com/apache/airflow/pull/36003 > > On Wed, Nov 29, 2023 at 10:05 AM Jarek Potiuk <ja...@potiuk.com> wrote: > >> Lazy consensus have been reached. I am going to change our tooling to >> mark latest available (3.12) as the "latest" image. >> >> On Wed, Nov 22, 2023 at 1:59 AM Jarek Potiuk <ja...@potiuk.com> wrote: >> >>> Hello everyone, >>> >>> Following the proposal >>> https://lists.apache.org/thread/xy192wmv6k1sy2wlx5vy64p678skrhko I >>> would like to ask for a Lazy consensus on making default docker image point >>> to "latest supported" version (so for 2.8.0 it would be 3.11). >>> >>> Reasoning and discussion available in the PROPOSAL thread above. I >>> believe we are generally OK with the move. There are some small concerns, >>> but generally it's mostly shifting time when users will have to deal with >>> the switch. >>> >>> There is no need to respond to it, if there will be no objections, lazy >>> consensus will be reached on Wednesday, 29th of November, 2:00 AM CET (1:00 >>> AM GMT) >>> >>> J. >>> >>
