Hello Team, We have hosted our prefect server with 2.14.11 version in ECS as a service. But in the UI settings, we could see that the recent version is 3.0.12, which should not be the case. I would like to understand the reason for this behaviour, and how the prefect updates are pushed in different operating systems. @Marvin, @Bianca Hoch, @Kevin Grismore - Your inputs would be much appreciated. Thank you !!

To address your issue, I'll investigate it by searching the Prefect documentation and GitHub issues. I'll focus on the behavior you're experiencing with Prefect version discrepancies on the UI and understand how updates are managed across different systems. Let me start by searching the Prefect 2.x and 3.x documentation to better understand any related information about version updates and UI behavior. I'll begin with the following queries: - "version discrepancies in UI" - "how prefect updates are managed" - "Prefect server update notifications" I'll run these queries now. Based on the Prefect documentation for both 2.x and 3.x, here are some insights regarding version discrepancies in the UI and how updates are managed: 1. Version Numbering: Prefect uses a versioning system composed of three parts: MAJOR.MINOR.PATCH. A change in any of these indicates a new release, with major changes being reserved for significant and widespread updates. 2. Version Discrepancies: The Prefect server UI might be programmed to show the most recent available version across Prefect's releases, which could account for differences observed if your installation does not automatically match the most recent version. This may not necessarily reflect your server's installed version but rather provide an alert for available updates. 3. Update Notifications: Prefect encourages updates but does not automatically push them across all platforms. Notifications for updates may appear in the UI to inform administrators of newer releases, allowing them to take necessary actions to upgrade if desired. 4. Client Compatibility: If you're running a Prefect server, you are responsible for maintaining compatibility with client versions. Prefect strives to maintain backwards compatibility, but newer clients may not work with older server versions. 5. Managing Upgrades: Using Prefect server commands, you can manage your server's database version through upgrades and downgrades. This includes commands like

prefect server database upgrade

to apply migrations necessary for new features or patches. For more detailed information, here are links to the relevant Prefect 2.x and 3.x documentation: - Prefect 2.x Versioning - Prefect 3.x Versioning If you're experiencing this issue due to an oversight in your server configuration or UI settings, reviewing your server's version and consulting these resources may aid in better understanding and resolving the discrepancy.

Hi Manoj, thanks for your message! If you're self hosting, there isn't a mechanism for us to upgrade your services for you. I'd check to see if anyone from your team pushed some changes on your end, maybe? 👀

So the version in the prefect UI settings reflect the actual version installed with the prefect self hosted server ? Is that what I should understand. Because the flow runs and UI features are almost the same. I read from the Marvin response that , the version could be linked to latest releases and not the installed version. I need some clarity of how the version is generated in the UI.

are you installing any integration packages where your server is hosted, like prefect-aws?

@Kevin Grismore , yes we do install and unfortunately in the prefect server we have not freezed the version for prefect-aws. So there is a possibility for this prefect-aws to install the latest packages when the container is spun up. I will try to freeze the version and will update the results. Thanks for the input Kevin !! 🙌 Update: I freezed the version of prefect-aws to 0.4.12 to match the version of prefect 2.14.11. But I'm getting the below error due to DB version mismtach I think and the server is not starting. We are passing the postgres database connection URL in task definition as env variable. alembic.util.exc.CommandError: Can't locate revision identified by 'eaec5004771f' @Bianca Hoch