@Marvin, how does backward compatibility work on the OSS version? Is there a page or resource where I can check this? Or should I assume that any client version can interact with the same server version under the major versions?

When it comes to backward compatibility in Prefect, here's a general overview based on the findings from both Prefect 2.x and 3.x documentation: 1. Server and Client Compatibility: - Prefect aims to maintain backward compatibility with older clients for each new server release. This means that older clients should generally work with newer server versions. - However, newer clients might not always be compatible with older server versions. This incompatibility is because the new client might rely on server features that aren't available in older versions. Therefore, it's recommended that all clients should be on the same version as the server or older. - Example: A client on version 2.1.0 can work with a server on version 2.5.0, but a client on 2.5.0 cannot work with a server on 2.1.0. 2. Prefect Cloud: - Prefect Cloud is designed to be compatible with all versions of Prefect clients. If you encounter any compatibility issues, reporting them is encouraged. 3. Deprecations and Changes: - Features might be deprecated in favor of improved alternatives, and deprecated features are generally retained for at least three minor version increases or six months, whichever is longer. - Bug fixes may change behavior but are not considered breaking changes. Here are the links to the resources I referred to: - Prefect 2.x Versioning and Compatibility - Prefect 3.x Versioning and Compatibility These links will provide you with more detailed information on the topic if needed!

That assumption is right @William Jamir and if it’s incorrect for any release that’s a fail / bug