👋 Very excited about the changes in 1.14 release! Had a question about this sentence in the release notes in the native support section

To experience the benefits of this change, upgrading flytekit to 1.14 is not enough. You have to also upgrade the flyte backend to 1.14.

Does this mean that even if I upgrade flytekit to 1.14.0, the messagepack serialization will not work unless other flyte components are upgraded to 1.14?

@crooked-lifeguard-46802 if the backend is not upgraded serialization will still use the "old" format. This change needs the backend to also be compatible with serializing and storing MessagePack bytes cc @damp-lion-88352

Yes @crooked-lifeguard-46802 this is a complete protocol change

Gotcha, and is the new backend compatible with

flytekit<1.14

? We have users that are on different flytekit versions, so trying to see if upgrading the backend could be done to enable

flytekit==1.14

Yes

cc @brash-london-45337 @echoing-kilobyte-84070 this might be worth looking into (for Jan)! • I think the new serialization changes solve a lot of our pain points (int to float, union types, offloading of large literals to prevent gRPC errors etc) • And if the new backend is compatible with older flytekit versions, it would also mean that we can migrate old workflows at our own pace and encourage new ones to use the 1.14

@crooked-lifeguard-46802 our philosophy is keep backend updated always, but maintain backwards compatibility