Guidance on Publishing Upgraded App Version & Rollback Options for Existing Marketplace App

Hi Team,
We have already published an app named Exotel CTI on the Freshdesk Marketplace. Currently, the platform version(v2.2) used in the existing app is deprecated, and we are working on upgrading the app to comply with the latest platform version.
I have a couple of questions regarding this:
Publishing the Upgraded Version:
What is the recommended process to publish this upgraded version so that it replaces the existing app on the Marketplace seamlessly, without causing issues for current users?
Rollback Procedure:
In case any issues arise post-upgrade, is there a supported rollback mechanism that allows us to revert to the previous stable version of the app? If so, how does that process work?
We want to ensure a smooth transition for our users and avoid any disruptions during or after the upgrade.

Regards,
Anant Prajapati
Exotel

@Anant_Prajapati

For publishing the upgraded version

If no app installation or settings are added or changed, the app can be auto-updated for all users on the last application version without any effort from the customers’ end.
They can still manually update it smoothly if they use one of the older app versions than the last version.

No other behavior changes for the users to upgrade the app from platform v2.2 to v2.3 or v3.0.

If any app installations or settings are added or changed, the users must provide them while updating the app. Auto-update cannot be enabled in this case, so all users have to update the app manually.

Rollback procedure

Freshworks platform doesn’t have the rollback feature. So, the only way to revert is to publish another version with the previous app version.
The auto-update feature is available on the platform, which will help push another version to all the users in the impacted app version that is to be reversed.

Let me know if you have further questions.