From 9a9c4009c6480fc2d5c12a38b02225d431a01485 Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Sun, 29 May 2022 10:27:21 +0200 Subject: [PATCH] Remove fixing cncf.kubernetes provider when generating constraints (#23994) When we yanked cncf.kubernetes provider, we pinned 3.1.2 temporarily for provider generation. This removes the pinning as we are already at 4.0.2 version --- scripts/in_container/_in_container_utils.sh | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/scripts/in_container/_in_container_utils.sh b/scripts/in_container/_in_container_utils.sh index c41e7af548e70..d6a637e5c348b 100644 --- a/scripts/in_container/_in_container_utils.sh +++ b/scripts/in_container/_in_container_utils.sh @@ -326,10 +326,8 @@ function install_all_providers_from_pypi_with_eager_upgrade() { # Installing it with Airflow makes sure that the version of package that matches current # Airflow requirements will be used. # shellcheck disable=SC2086 - # NOTE! Until we unyank the cncf.kubernetes provider, we explicitly install yanked 3.1.2 version - # TODO:(potiuk) REMOVE IT WHEN provider is released pip install -e ".[${NO_PROVIDERS_EXTRAS}]" "${packages_to_install[@]}" ${EAGER_UPGRADE_ADDITIONAL_REQUIREMENTS} \ - --upgrade --upgrade-strategy eager apache-airflow-providers-cncf-kubernetes==3.1.2 + --upgrade --upgrade-strategy eager }