Late to the party, but +1 for sure Jarek Potiuk <[email protected]> 於 2026年2月28日週六 下午11:57寫道：
> BTW. The grpcio 1.78.1 has been yanked - because it caused issues with > serverless GCP environment https://github.com/grpc/grpc/issues/41725 so I > guess this will take more time for Apache Beam will release a version that > we will be able to use. I have to rebuild 3.12 image of 2.11.1 because of > that. > > On Fri, Feb 27, 2026 at 3:17 PM Jarek Potiuk <[email protected]> wrote: > > > Agreed. > > > > On Fri, Feb 27, 2026 at 2:27 PM Kaxil Naik <[email protected]> wrote: > > > >> tbh I don't think we need to wait for Monday -- given we know we are > >> waiting for upstream dep fix which isn't happening until then anyway and > >> we > >> are in agreement that this needs to happen and is short-term thing. > >> > >> I'll go ahead and merge your PR > >> > >> On Fri, 27 Feb 2026 at 11:23, Pierre Jeambrun <[email protected]> > >> wrote: > >> > >> > +1 > >> > > >> > On Fri 27 Feb 2026 at 08:47, Vikram Koka via dev < > >> [email protected]> > >> > wrote: > >> > > >> > > +1 > >> > > > >> > > > >> > > On Thu, Feb 26, 2026 at 10:49 PM Jarek Potiuk <[email protected]> > >> wrote: > >> > > > >> > > > +1 (though not needed) I hope it will be unsuspended quickly :) > >> > > > > >> > > > On Fri, Feb 27, 2026, 01:32 Kaxil Naik <[email protected]> > wrote: > >> > > > > >> > > > > +1 > >> > > > > > >> > > > > On Thu, 26 Feb 2026 at 22:09, Pavankumar Gopidesu < > >> > > > [email protected] > >> > > > > > > >> > > > > wrote: > >> > > > > > >> > > > > > Hello everyone, > >> > > > > > > >> > > > > > I would like to call for a lazy consensus to suspend the > Apache > >> > Beam > >> > > > > > provider. This suspension is necessary due to a grpcio > >> limitation > >> > > that > >> > > > is > >> > > > > > currently blocking the development of new providers and other > >> > > > > dependencies. > >> > > > > > > >> > > > > > I prepared a PR to do so: > >> > > https://github.com/apache/airflow/pull/61926 > >> > > > . > >> > > > > > and you can read more about consequences of suspension in > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > https://github.com/apache/airflow/blob/main/PROVIDERS.rst#suspending-releases-for-providers > >> > > > > > > >> > > > > > Discussion Thread: > >> > > > > > > >> https://lists.apache.org/thread/s0y610cdn2t1hq2mg6y3xws02bskp89w ( > >> > > > > > > >> https://lists.apache.org/thread/s0y610cdn2t1hq2mg6y3xws02bskp89w) > >> > > > > > > >> > > > > > Lazy Consensus Period: > >> > > > > > The lazy consensus is open until Monday, March 2nd, at 11 PM > >> GMT. > >> > > > > > > >> > > > > > In accordance with lazy consensus rules, a formal vote is not > >> > > required; > >> > > > > the > >> > > > > > absence of binding dissent will be considered approval. > >> > > > > > > >> > > > > > Justification: > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > ---------------------------------------------------------------------------------------------------------------- > >> > > > > > Suspending apache-airflow-providers-apache-beam package. > >> > > > > > > >> > > > > > The current Apache Beam Python SDK pins grpcio restricts it > to a > >> > > range > >> > > > > like > >> > > > > > <1.66. > >> > > > > > > >> > > > > > This old grpcio version conflicts with several other > >> dependencies > >> > in > >> > > > the > >> > > > > > project workspace, especially when using uv sync. > >> > > > > > > >> > > > > > Newer versions of opentelemetry-exporter-otlp / > >> opentelemetry-proto > >> > > > that > >> > > > > > need updated protobuf / grpcio > >> > > > > > pydantic-ai-slim (used in common-ai provider) requiring > >> > > > > opentelemetry-api ≥ > >> > > > > > 1.28.0 > >> > > > > > > >> > > > > > This blocks development work (including AIP-99) and prevents > >> > bumping > >> > > > > other > >> > > > > > dependencies across the repo. the PR is here #61794 where its > >> > failing > >> > > > > > currently due to the limitation of several dependencies > pinned. > >> > > > > > > >> > > > > > The grpcio upper bound issue in Apache Beam has been known > for a > >> > > while, > >> > > > > and > >> > > > > > its raised already @potiuk apache/beam#34081 long ago. > >> > > > > > > >> > > > > > The root cause is being addressed upstream in the gRPC project > >> > > > > > grpc/grpc#37710 > >> > > > > > (they have already fixed it, with a possible release in grpcio > >> > 1.78.1 > >> > > > or > >> > > > > a > >> > > > > > patch that should lift most of these pins/conflicts) > >> > > > > > > >> > > > > > Following the official guidelines for provider suspension: > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > https://github.com/apache/airflow/blob/main/PROVIDERS.rst#suspending-releases-for-providers > >> > > > > > > >> > > > > > The Apache beam provider can be removed from suspension by a > PR > >> > > > reverting > >> > > > > > this change once grpcio limitation removed from the > apache-beam. > >> > > > > > > >> > > > > > Regards, > >> > > > > > Pavan > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > > >
