Back in May/2022 the grpc team announced that they were publishing a new major version of the

protobuf

library. As expected, this major version was gradually picked up by the python ecosystem, including some of

flytekit

dependencies, specifically

grpcio

and

grpcio-status

which picked up this change in version 1.50. This explains why

flytekit

restricted the versions of those libraries starting on flytekit 1.2.4. In other words, we have to constrain the versions of those libraries until we are able to update

protobuf

to the new major version. This brings us to

flyteidl

, which is the component that actually generates the protobuf stubs and has the constraint on the

protobuf

library. We’re working to update

protobuf

and recently we published two incomplete patch versions of

flyteidl

(1.2.6 and 1.2.7), which were yanked. The expectation is that we’re going to publish a new minor version of

flyteidl

shortly and also publish a new version of

flytekit

, both of which will start to use the new major version of

protobuf

, at which time we can remove the

flytekit

constraints on

grpcio

.