Is there a way to mitigate breaking changes and/or major versions in a CA template?
One app I manage a template for has a new major (x.y.z) version out, which requires changes to both the Docker/CA settings (some new config fields, some removed, some changed type from a string to a dropdown option) and to non-Docker settings (permission changes to the remote API the app interacts with via the provider's portal).
1. Is there a process that I can take to properly migrate user settings from the old "string" type to the new "dropdown" type? If not, is there a way to call this out to the user or force them to view the app's configuration page during an update?
2. In the same vain, is there a way to stop users from auto-updating to a new major version, or bring attention to it?
It doesn't seem like there's necessarily versioning for CA templates. The container currently uses `Branch` for which Docker image to use, but with `latest` being the only option. Perhaps changing the only available branch to a specific older image?