olegkachur-e opened a new issue, #66551: URL: https://github.com/apache/airflow/issues/66551
### Under which category would you file this issue? Providers ### Apache Airflow version version 3 ### What happened and how to reproduce it? The beam provider has been [suspended](https://github.com/apache/airflow/pull/61926) a while ago, because of beam python sdk dependency for the grpcio constraint. The constraint issue seems to be [resolved](https://github.com/apache/beam/pull/37633) and [released](https://github.com/apache/beam/milestone/40?closed=1) in a version of beam python sdk v.2.72.0. ### What you think should happen instead? So provider can be brought back in a "regular" status, being released and maintained. ### Operating System _No response_ ### Deployment None ### Apache Airflow Provider(s) apache-beam ### Versions of Apache Airflow Providers _No response_ ### Official Helm Chart version Not Applicable ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _No response_ ### Anything else? I need community guidance on how to "un-suspend" the provider? Is it as straightforward as just reverting the https://github.com/apache/airflow/pull/61926? I don't mind submitting a PR if needed. ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
