Hello everyone. I am happy to announce that I just merged https://github.com/apache/airflow/pull/66952, which unsuspends the Apache Beam provider. Cross my fingers we don't find any blockers preventing the release with apache-beam 2.76.0; it should be included in the upcoming wave of Provider's releases (starting this week).
Thanks to everyone for cooperating on this matter. This was a rather long one, but I think the end result is that both Airflow and Beam dependencies are fresher, which will also enable future "faster" dependency moves in the future. Given the current state of Supply Chain / Security issues (roughly a 10x increase in reported issues being fixed by nearly everyone), unblocking faster upgrade paths for our dependencies is crucial. For reference: Yesterday's Microsoft Patch Tuesday included 914 issues, 21 of which were critical, and 2 are currently actively exploited. https://senserva.com/patch-tuesday.html#history This chart looks very similar across the board: [image: Screenshot 2026-09-09 at 15.16.54.png] J. On Mon, Jul 27, 2026 at 4:51 PM Jarek Potiuk <[email protected]> wrote: > Yes. Our next release is planned for 4th of Aug, however, if we need to > support an unsuspended provider like Beam, it might be more involved. I > would say we will anyhow have to make an exception ad-hoc release whenever > Beam is released - that seems quite a bit safer than mixing it with other > provider releases. > > We have to account for the four-day cooldown required for installing > dependencies and rebasing and merging the "revert" PR and add >= 2.76.0 > (there might be some surprises to fix - dependency resolution is too > complex to make 100% predictions. > This means that whenever Beam client 2.76.0 is released, we will either > need to wait 4 days or add a temporary exception to the cooldown (and > remove it after), and make sure that all our tests pass after we add >= > 2.76.0 in our deps. > So it's anyhow a more involved thing than a regular release. > > I would say releasing 2.76.Releasing 2.76.0 by the end of July could allow > us to add it to the "regular" wave to give us time to do all that - so I'd > say it's quite unlikely. > > J. >
