Hi Everyone, Following Jarek's outreach to the Apache Beam team, there has been significant progress: the gRPC team released a fix, and the Beam team has already merged it. However, it remains unclear when a new version of Beam will be officially released.
According to their project milestone, the next release appears to be due at the end of March [1] Given this timeline, I would like to move forward with a lazy consensus to suspend the provider for now. We can always restore it once the fix is officially released. [1]: https://github.com/apache/beam/milestone/40 Best regards, Pavan On Mon, Feb 16, 2026 at 8:17 AM Jarek Potiuk <[email protected]> wrote: > Yep. We should wait - they intend to release this Wed. And they thanked us > for raising awareness about the urgency :) > > On Mon, Feb 16, 2026, 07:14 Amogh Desai <[email protected]> wrote: > > > Was following the beam devlist and I noticed this: > > https://lists.apache.org/thread/qnw70bvwn0pgopdzr5vc66txkbw86ynv > > > > It seems that they will have a fix for this issue with a release on > > Wednesday, just two days from now. > > If that turns out to be the case, we will not need to suspend beam over > > here. > > > > Thanks & Regards, > > Amogh Desai > > > > > > On Mon, Feb 16, 2026 at 4:07 AM Pavankumar Gopidesu < > > [email protected]> > > wrote: > > > > > Thanks Jarek, for raising the discussion in beam devlist. > > > > > > Regards, > > > Pavan > > > > > > On Sun, Feb 15, 2026 at 3:48 PM Jarek Potiuk <[email protected]> wrote: > > > > > > > Started discussion at beam devlist > > > > https://lists.apache.org/thread/qnw70bvwn0pgopdzr5vc66txkbw86ynv > > > > > > > > On Sun, Feb 15, 2026 at 4:16 PM Jarek Potiuk <[email protected]> > wrote: > > > > > > > > > I am +1 on this. I am also going to start a discussion on a beam > > > devlist > > > > > for it . They seem to be really close to fix it, and release new > > > > versions - > > > > > needs grpcio release 1.78.1 first and I believe apache beam team > can > > > > > influence it. > > > > > > > > > > Thanks Pavan for all the work to test it - the > > > > > > > > > > > > > > > https://github.com/apache/airflow/actions/runs/22037156266/job/63672341133?pr=61926#step:6:1366 > > > > > nicely shows what kind of problems we are talking about: > > > > > > > > > > Below is an example of what apache.beam is currently blocking us > from > > > > > upgrading to in Python 3.10 - it's a huge "drag" on our > dependencies. > > > > > > > > > > J. > > > > > > > > > > > > > > > ---- > > > > > > > > > > 80d79 > > > > > < apache-beam==2.71.0 > > > > > 130d128 > > > > > < beartype==0.22.9 > > > > > 132d129 > > > > > < betterproto==1.2.5 > > > > > 172c169 > > > > > < cryptography==42.0.8 > > > > > --- > > > > > > cryptography==44.0.3 > > > > > 201d197 > > > > > < envoy_data_plane==0.1.0 > > > > > 212d207 > > > > > < fasteners==0.20 > > > > > 234c229 > > > > > < google-auth-httplib2==0.2.1 > > > > > --- > > > > > > google-auth-httplib2==0.3.0 > > > > > 275c270 > > > > > < google-cloud-storage==2.19.0 > > > > > --- > > > > > > google-cloud-storage==3.4.1 > > > > > 294,296c289,291 > > > > > < grpcio-status==1.62.3 > > > > > < grpcio==1.65.5 > > > > > < grpclib==0.4.9 > > > > > --- > > > > > > grpcio-status==1.71.2 > > > > > > grpcio-tools==1.71.2 > > > > > > grpcio==1.78.0 > > > > > 308c303 > > > > > < httplib2==0.22.0 > > > > > --- > > > > > > httplib2==0.31.2 > > > > > 325,326c320,321 > > > > > < immutabledict==4.3.0 > > > > > < importlib_metadata==8.4.0 > > > > > --- > > > > > > immutabledict==4.3.1 > > > > > > importlib_metadata==8.7.1 > > > > > 351d345 > > > > > < jsonpickle==3.4.2 > > > > > 427d420 > > > > > < objsize==0.7.1 > > > > > 437,447c430,441 > > > > > < opensearch-py==3.0.0 > > > > > < opentelemetry-api==1.27.0 > > > > > < opentelemetry-exporter-otlp-proto-common==1.27.0 > > > > > < opentelemetry-exporter-otlp-proto-grpc==1.27.0 > > > > > < opentelemetry-exporter-otlp-proto-http==1.27.0 > > > > > < opentelemetry-exporter-otlp==1.27.0 > > > > > < opentelemetry-exporter-prometheus==0.48b0 > > > > > < opentelemetry-proto==1.27.0 > > > > > < opentelemetry-resourcedetector-gcp==1.9.0a0 > > > > > < opentelemetry-sdk==1.27.0 > > > > > < opentelemetry-semantic-conventions==0.48b0 > > > > > --- > > > > > > opensearch-protobufs==0.19.0 > > > > > > opensearch-py==3.1.0 > > > > > > opentelemetry-api==1.39.1 > > > > > > opentelemetry-exporter-otlp-proto-common==1.39.1 > > > > > > opentelemetry-exporter-otlp-proto-grpc==1.39.1 > > > > > > opentelemetry-exporter-otlp-proto-http==1.39.1 > > > > > > opentelemetry-exporter-otlp==1.39.1 > > > > > > opentelemetry-exporter-prometheus==0.60b1 > > > > > > opentelemetry-proto==1.39.1 > > > > > > opentelemetry-resourcedetector-gcp==1.11.0a0 > > > > > > opentelemetry-sdk==1.39.1 > > > > > > opentelemetry-semantic-conventions==0.60b1 > > > > > 493c487 > > > > > < protobuf==4.25.8 > > > > > --- > > > > > > protobuf==5.29.6 > > > > > 503,504c497 > > > > > < pyarrow-hotfix==0.7 > > > > > < pyarrow==18.1.0 > > > > > --- > > > > > > pyarrow==23.0.0 > > > > > 561c554 > > > > > < ray==2.47.1 > > > > > --- > > > > > > ray==2.53.0 > > > > > 609c602 > > > > > < snowflake-connector-python==4.0.0 > > > > > --- > > > > > > snowflake-connector-python==4.3.0 > > > > > 642d634 > > > > > < stringcase==1.2.0 > > > > > 726c718 > > > > > < yandexcloud==0.328.0 > > > > > --- > > > > > > yandexcloud==0.377.0 > > > > > > > > > > J. > > > > > > > > > > > > > > > On Sun, Feb 15, 2026 at 3:42 PM Pavankumar Gopidesu < > > > > > [email protected]> wrote: > > > > > > > > > >> Hi Everyone, > > > > >> > > > > >> I would like to propose suspending the apache-beam provider, until > > the > > > > >> grpcio version limitation in Apache Beam is resolved upstream. > > > > >> > > > > >> The current apache-beam Python SDK imposes a restrictive upper > bound > > > on > > > > >> grpcio (e.g., <1.66), which creates significant dependency > > resolution > > > > >> conflicts. This becomes problematic when our CI uv sync, and it > > blocks > > > > >> progress on several fronts. > > > > >> > > > > >> I have observed few key issues: > > > > >> > > > > >> Conflicts arise during dependency resolution when working on > AIP-99 > > > with > > > > >> the latest pydantic-ai version, resolution fails entirely, though > it > > > > >> succeeds using the outdated pydantic-ai 0.0.5. > > > > >> > > > > >> Newer versions of opentelemetry-exporter-otlp / > opentelemetry-proto > > > > demand > > > > >> updated protobuf and grpcio. > > > > >> pydantic-ai-slim (utilized in the common-ai provider) requires > > > > >> opentelemetry-api >= 1.28.0. > > > > >> > > > > >> These constraints prevent dependency upgrades across the > repository > > > and > > > > >> stall development efforts, for AIP-99. For example, PR [1] is > > > currently > > > > >> failing due to these pinned limitations. > > > > >> > > > > >> This grpcio upper-bound restriction in Apache Beam has been a > known > > > > issue > > > > >> for some time, and Jarek has already raised this long ago see the > > > > upstream > > > > >> issue [2] . The root cause traces back to the gRPC project [3], > > where > > > > >> fixes > > > > >> have already landed, with expectations that a release like grpcio > > > 1.78.1 > > > > >> (or a targeted patch) will remove most of these pins and > conflicts. > > > > >> > > > > >> In line with the Airflow provider suspension guidelines [4], I > would > > > > like > > > > >> to suspend apache beam provider and I have a PR draft in progress > > [5]. > > > > >> > > > > >> Please let me know your thoughts on this. > > > > >> > > > > >> [1]: https://github.com/apache/airflow/pull/61794 > > > > >> [2]: https://github.com/apache/beam/issues/34081 > > > > >> [3]: https://github.com/grpc/grpc/issues/37710 > > > > >> [4]: > > > > >> > > > > >> > > > > > > > > > > https://github.com/apache/airflow/blob/main/PROVIDERS.rst#suspending-releases-for-providers > > > > >> [5]: https://github.com/apache/airflow/pull/61926 > > > > >> > > > > >> Regards, > > > > >> Pavan > > > > >> > > > > > > > > > > > > > > >
