|
| 1 | +# After any updates to this file, requirements.txt should be regenerated running |
| 2 | +# the following in this folder: |
| 3 | +# pip-compile --no-emit-index-url requirements.in |
| 4 | + |
| 5 | +click==8.1.8 |
| 6 | +click-option-group==0.5.7 |
| 7 | +docstring-parser>=0.7.3,<1 |
| 8 | +# Pin google-api-core version for the bug fixing in 1.31.5 |
| 9 | +# https://github.com/googleapis/python-api-core/releases/tag/v1.31.5 |
| 10 | +google-api-core>=1.31.5,<3.0.0dev,!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.0 |
| 11 | +google-auth>=1.6.1,<3 |
| 12 | +# https://github.com/googleapis/python-storage/blob/main/CHANGELOG.md#221-2022-03-15 |
| 13 | +google-cloud-storage>=2.2.1,<4 |
| 14 | +# pin kfp-pipeline-spec to an exact version, since this is the contract between a given KFP |
| 15 | +# SDK version and the BE. we don't want old version of the SDK to write new fields and to |
| 16 | +# have the BE reject the new unsupported field (even if the new field backward compatible from a proto perspective) |
| 17 | +kfp-pipeline-spec==2.14.0 |
| 18 | +# Update the upper version whenever a new major version of the |
| 19 | +# kfp-server-api package is released. |
| 20 | +# Update the lower version when kfp sdk depends on new apis/fields in |
| 21 | +# kfp-server-api |
| 22 | +kfp-server-api>=2.14.0,<3 |
| 23 | +kubernetes>=8.0.0,<31 |
| 24 | +# protobuf version should be identical to the one in kfp-pipeline-spec |
| 25 | +# api/v2alpha1/python/requirements.txt |
| 26 | +protobuf==6.31.1,<7.0 |
| 27 | +PyYAML>=5.3,<7 |
| 28 | +requests-toolbelt>=0.8.0,<2 |
| 29 | +tabulate>=0.8.6,<1 |
| 30 | +urllib3<3.0.0 |
| 31 | + |
| 32 | +## standard library backports ## |
| 33 | +typing-extensions>=3.7.4,<5; python_version<"3.9" |
0 commit comments