Bump minimum Airflow version in providers (#30917)

According to our policy https://github.com/apache/airflow/blob/main/PROVIDERS.rst#minimum-supported-version-of-airflow-for-community-managed-providers

Author: eladkal

.github/workflows/ci.yml

@@ -766,7 +766,7 @@ jobs:
 
   provider-airflow-compatibility-check:
     timeout-minutes: 80
-    name: "Providers Airflow 2.3 compatibility check"
+    name: "Providers Airflow 2.4 compatibility check"
     runs-on: "${{needs.build-info.outputs.runs-on}}"
     needs: [build-info, wait-for-ci-images]
     env:
@@ -789,10 +789,10 @@ jobs:
         run: >
           breeze release-management prepare-provider-packages --version-suffix-for-pypi dev0
           --package-format wheel ${{ needs.build-info.outputs.affected-providers-list-as-string }}
-      - name: "Fix incompatible 2.3 provider packages"
+      - name: "Fix incompatible 2.4 provider packages"
         run: |
-          # This step should remove the provider packages that are not compatible with 2.3
-          # or replace them with 2.3 compatible versions. Sometimes we have good reasons to bump
+          # This step should remove the provider packages that are not compatible with 2.4
+          # or replace them with 2.4 compatible versions. Sometimes we have good reasons to bump
           # the min airflow versions for some providers and then we need to add exclusions here.
           #
           # The Removal can be done with:
@@ -813,15 +813,15 @@ jobs:
           providers = json.loads(Path("generated/provider_dependencies.json").read_text())
           provider_keys = ",".join(providers.keys())
           print("AIRFLOW_EXTRAS={}".format(provider_keys))' >> $GITHUB_ENV
-      - name: "Install and verify all provider packages and airflow on Airflow 2.3 files"
+      - name: "Install and verify all provider packages and airflow on Airflow 2.4 files"
         run: >
-          breeze release-management verify-provider-packages --use-airflow-version 2.3.0
-          --use-packages-from-dist --airflow-constraints-reference constraints-2.3.0
+          breeze release-management verify-provider-packages --use-airflow-version 2.4.0
+          --use-packages-from-dist --airflow-constraints-reference constraints-2.4.0
         if: needs.build-info.outputs.affected-providers-list-as-string == ''
-      - name: "Install affected provider packages and airflow on Airflow 2.3 files"
+      - name: "Install affected provider packages and airflow on Airflow 2.4 files"
         run: >
-          breeze release-management install-provider-packages --use-airflow-version 2.3.0
-          --airflow-constraints-reference constraints-2.3.0 --run-in-parallel
+          breeze release-management install-provider-packages --use-airflow-version 2.4.0
+          --airflow-constraints-reference constraints-2.4.0 --run-in-parallel
         # Make sure to skip the run if the only provider to be installed has been removed
         # in the previous step
         if: >

PROVIDERS.rst

@@ -120,8 +120,8 @@ Airflow version to the next MINOR release, when 12 months passed since the first
 MINOR version of Airflow.
 
 For example this means that by default we upgrade the minimum version of Airflow supported by providers
-to 2.4.0 in the first Provider's release after 30th of April 2023. The 30th of April 2022 is the date when the
-first ``PATCHLEVEL`` of 2.3 (2.3.0) has been released.
+to 2.5.0 in the first Provider's release after 19th of September 2023. The 19th of September 2022 is the date when the
+first ``PATCHLEVEL`` of 2.4 (2.4.0) has been released.
 
 When we increase the minimum Airflow version, this is not a reason to bump ``MAJOR`` version of the providers
 (unless there are other breaking changes in the provider). The reason for that is that people who use

airflow/providers/airbyte/provider.yaml

@@ -36,7 +36,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - apache-airflow-providers-http
 
 integrations:

airflow/providers/alibaba/provider.yaml

@@ -34,7 +34,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - oss2>=2.14.0
 
 integrations:

airflow/providers/amazon/provider.yaml

@@ -57,7 +57,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - apache-airflow-providers-common-sql>=1.3.1
   - boto3>=1.24.0
   - asgiref

airflow/providers/apache/beam/provider.yaml

@@ -41,7 +41,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - apache-beam>=2.33.0
 
 integrations:

airflow/providers/apache/cassandra/provider.yaml

@@ -36,7 +36,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - cassandra-driver>=3.13.0
 
 integrations:

airflow/providers/apache/drill/provider.yaml

@@ -37,7 +37,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - apache-airflow-providers-common-sql>=1.3.1
   - sqlalchemy-drill>=1.1.0
 

airflow/providers/apache/druid/provider.yaml

@@ -43,7 +43,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - apache-airflow-providers-common-sql>=1.3.1
   - pydruid>=0.4.1
 

airflow/providers/apache/flink/provider.yaml

@@ -27,7 +27,7 @@ versions:
   - 1.0.0
 
 dependencies:
-  - apache-airflow>=2.3.0
+  - apache-airflow>=2.4.0
   - cryptography>=2.0.0
   - apache-airflow-providers-cncf-kubernetes>=5.1.0