Skip to content

Un-suspend apache-airflow-providers-apache-beam #66551

Closed

Description

@olegkachur-e

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 a while ago, because of beam python sdk dependency for the grpcio constraint.

The constraint issue seems to be resolved and released 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 #61926?

I don't mind submitting a PR if needed.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. added
    kind:bugThis is a clearly a bug
    needs-triagelabel for new issues that we didn't triage yet
    on May 7, 2026
  2. olegkachur-e commented on May 7, 2026

    @olegkachur-e
    ContributorAuthor
  3. olegkachur-e commented on May 7, 2026

    @olegkachur-e
    ContributorAuthor

    I took a look on: https://github.com/apache/airflow/blob/main/providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst#suspending-releases-for-providers it suggests:

    The suspension will be lifted when the dependencies of the provider are made compatible with the Apache Airflow and with other providers - by merging a PR that removes the suspension and succeeds.

    So I'll try to revert the suspension PR.

  4. potiuk commented on May 9, 2026

    @potiuk
    Member

    Happy to help!

  5. 4 remaining items

  6. added
    kind:taskA task that needs to be completed as part of a larger issue
    and removed
    kind:bugThis is a clearly a bug
    needs-triagelabel for new issues that we didn't triage yet
    on Jul 3, 2026
  7. shahar1 commented on Sep 18, 2026

    @shahar1
    Contributor

    Unsuspended :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions