chore: Pin kfp-pipeline-spec==0.4.0, relax kfp-server-api to <2.4.0

Signed-off-by: Chen Sun <chensun@users.noreply.github.com>
kubeflow · Sep 9, 2024 · 0780426 · 0780426
1 parent 3897764
commit 0780426
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/sdk/python/requirements.in b/sdk/python/requirements.in
@@ -11,12 +11,12 @@ google-auth>=1.6.1,<3
 # https://github.com/googleapis/python-storage/blob/main/CHANGELOG.md#221-2022-03-15
 google-cloud-storage>=2.2.1,<3
 # pin kfp-pipeline-spec to an exact version, since this is the contract between a given KFP SDK version and the BE. we don't want old version of the SDK to write new fields and to have the BE reject the new unsupported field (even if the new field backward compatible from a proto perspective)
-kfp-pipeline-spec==0.3.0
+kfp-pipeline-spec==0.4.0
 # Update the upper version whenever a new major version of the
 # kfp-server-api package is released.
 # Update the lower version when kfp sdk depends on new apis/fields in
 # kfp-server-api.
-kfp-server-api>=2.0.0,<2.1.0
+kfp-server-api>=2.0.0,<2.4.0
 kubernetes>=8.0.0,<31
 protobuf>=4.21.1,<5
 PyYAML>=5.3,<7

diff --git a/sdk/python/requirements.txt b/sdk/python/requirements.txt
@@ -43,9 +43,9 @@ googleapis-common-protos==1.63.2
     # via google-api-core
 idna==3.7
     # via requests
-kfp-pipeline-spec==0.3.0
+kfp-pipeline-spec==0.4.0
     # via -r requirements.in
-kfp-server-api==2.0.5
+kfp-server-api==2.3.0
     # via -r requirements.in
 kubernetes==30.1.0
     # via -r requirements.in