+1 (non-binding) - Ran the regression suite and example DAGs. - Performed UI sanity checks.
On Wed, 11 Mar 2026 at 11:29, Amogh Desai <[email protected]> wrote: > +1 binding. > > - Ran SVN check > - Performed reproducible package checks > - Signatures > - Checksums > - Licenses > > Installed the RC bits for 2.11.2rc1 with breeze and did some > random UI clicks and ran some of my dags, all looks ok. > > Jens -- I feel you :) > > > Thanks & Regards, > Amogh Desai > > > On Wed, Mar 11, 2026 at 4:38 AM Jens Scheffler <[email protected]> > wrote: > > > +1 (binding) - Checked SVN, Reproducible package build, Licenses, > > Signatures > > > > After one week of working with Airflow 3.1 using Airflow 2.11 feels like > > being in 1980 :-D > > > > Did run one Dag from examples after runnign with Breeze, basic tests > > only and looks OK. > > > > P.S.: uff, 4 release validations in one evening, looking forward to ATR > :-D > > > > On 09.03.26 21:01, Jarek Potiuk wrote: > > > Small update: I found minor formatting issue in the "frontend change > > > summary" - and in Github UI it caused the high-risk table to not render > > > > > > https://github.com/apache/airflow/blob/v2-11-test/airflow/www/changes_in_2_11_dependencies.rst > > > is a better link (I pushed a fix to v2-11-test) > > > > > > On Mon, Mar 9, 2026 at 8:54 PM Jarek Potiuk <[email protected]> wrote: > > > > > >> Hey fellow Airflowers, > > >> > > >> I have cut Airflow 2.11.2rc1. This email is calling a vote on the > > release, > > >> which will last at least 72 hours, from Monday, March 9, 2026 at 9 pm > > CET > > >> until Thursday, March 12, 2021 at 9pm, CET and until 3 binding +1 > votes > > >> have been received. > > >> > > >> > > >> > > > https://www.timeanddate.com/countdown/generic?p0=1440&iso=20260312T20&msg=Release > > >> > > >> Status of testing of the release is kept in > > >> https://github.com/apache/airflow/issues/63214 > > >> > > >> Consider this my (binding) +1. > > >> > > >> Airflow 2.11.2rc1 is available at: > > >> https://dist.apache.org/repos/dist/dev/airflow/2.11.2rc1/ > > >> > > >> *apache-airflow-2.11.2-source.tar.gz* is a source release that comes > > with > > >> INSTALL instructions. > > >> *apache-airflow-2.11.2.tar.gz* is the binary Python "sdist" release. > > >> *apache_airflow-2.11.2-py3-none-any.whl* is the binary Python wheel > > >> "binary" release. > > >> > > >> Public keys are available at: > > >> https://dist.apache.org/repos/dist/release/airflow/KEYS > > >> > > >> Please vote accordingly: > > >> > > >> [ ] +1 approve > > >> [ ] +0 no opinion > > >> [ ] -1 disapprove with the reason > > >> > > >> Only votes from PMC members are binding, but all members of the > > community > > >> are encouraged to test the release and vote with "(non-binding)". > > >> > > >> The test procedure for PMC members is described in: > > >> > > >> > > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md#verify-the-release-candidate-by-pmc-members > > >> > > >> The test procedure for contributors and members of the community who > > would > > >> like to test this RC is described in: > > >> > > >> > > > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md#verify-the-release-candidate-by-contributors > > >> > > >> Please note that the version number excludes the `rcX` string, so it's > > now > > >> simply 2.11.2. This will allow us to rename the artifact without > > modifying > > >> the artifact checksums when we actually release. > > >> > > >> Release Notes: > > >> https://github.com/apache/airflow/blob/2.11.2rc1/RELEASE_NOTES.rst > > >> > > >> The images are pushed > > >> https://hub.docker.com/r/apache/airflow/tags?name=2.11.2 > > >> Doc publishing will take a bit more time - I will update it here when > > docs > > >> are ready (but besides release notes there are hardly any changes) > > >> > > >> For information on what goes into a release please see: > > >> > > > https://github.com/apache/airflow/blob/main/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md > > >> > > >> > > >> *Scope of the changes* > > >> This is a follow-up release after 2.11.1, and addresses a few issues > > found > > >> in 2.11.1 - those are rather small annoying issues found due to > > connexion > > >> migration and very few small fixes backported from Airflow 3. > > >> > > >> However a bit bigger change, is *upgrade of UI/npm dependencies > (many).* > > >> Airflow 2 contains embedded / compiled UI javascript code for the UI > and > > >> those can only be upgraded with new airflow release. Since we are just > > >> about to reach EOL for Airflow 2, this release attempts to migrate to > > >> latest "reasonable" versions of those dependencies. Not everything > > could be > > >> migrated to "latest latest" release - but at least where we could we > > >> migrated to latest minor/patchlevel upgrades. We are using it as a > last > > >> chance to bump to latest versions. Once Airflow 2 reaches EOL, the > only > > way > > >> to upgrade those UI dependencies will be to migrate to Airflow 3. > > >> > > >> Therefore, there **might** be some UI glitches that we missed while > > >> manually testing the RC - so I have a kind request to those who will > be > > >> testing it to pay extra attentions on those areas afected potentially > by > > >> the migration. > > >> > > >> Together with Claude, I prepared a nice overview of everything > migrated > > in > > >> 2.11.2 from the UI dependencies - together with splitting it to > > >> high/medium/low risk and performing an (AI) assesment of whether there > > is > > >> an impact on our code, lookling at the way how we use the dependecies. > > >> > > >> You can see the report here: > > >> > > > https://github.com/apache/airflow/blob/2.11.2rc1/airflow/www/changes_in_2_11_dependencies.rst > > >> > > >> > > >> The summary is as follows. I would love to hear more from those more > > >> familiar with the UI who can take a look and verify that the > assessment > > >> holds. I did brief manual verification that none of the potentia areas > > are > > >> affected, but I might have missed some, so kindly ask for > > re-verification > > >> > > >> > > >> *Final conclusion:* > > >> > > >> - React 19 (^18 → ^19.2.4) — Impact: LOW despite being a major > bump > > -> > > >> Verdict: Runtime likely fine, but TypeScript compilation may break > > on > > >> implicit children > > >> - Jest 30 (^27 → ^30) — Impact: MEDIUM-HIGH -> MEDIUM IMPACT (may > > >> cause visual or functional differences) > > >> - echarts 6 — Impact: MEDIUM (4 files) -> Chart rendering defaults > > may > > >> change — visual verification needed > > >> - react-router-dom v7 (^6 → ^7) — Impact: LOW despite major bump > -> > > >> Verdict: Likely works without changes > > >> - react-markdown 10 (^8 → ^10) — Impact: MEDIUM (1 file) -> Plugin > > API > > >> (remarkPlugins) and components prop may have changed > > >> - elkjs 0.11 (^0.7 → ^0.11) — Impact: LOW-MEDIUM (4 files) -> > Layout > > >> algorithm changes may render DAG graphs differently — visual > > verification > > >> needed > > >> - framer-motion 11 (^6 → ^11) — Impact: LOW (1 file only) -> > Should > > >> work but worth a visual check on tooltip animations > > >> > > >> All the rest is low risk. > > >> > > >> > > >> > > >> *Recommended verification order:* > > >> Visual check: echarts charts, DAG graph layouts (elkjs), tooltip > > >> animations, swagger API docs page > > >> > > >> ... > > >> > > >> Cheers, > > >> Jarek > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- Regards, Atul Singh
