Currently, when using a custom app extension action or source block in Shopify Flow, any newly released version of the extension requires manually updating each workflow. This involves deleting the old extension block and replacing it with the new one to ensure the latest version is in effect. This manual process can be tedious, especially for merchants managing multiple workflows.
Proposed Features:
“Opt into Latest Version” Button:
A button on the block that allows merchants to automatically update to the latest version of the app extension without manually replacing it in each workflow.
This ensures workflows always use the most up-to-date version without disruption.
Version Selection for App Extensions:
A dropdown or selection feature that allows admins to choose which version of the extension to use.
This would give merchants control over whether they want to update to a new version or continue using a previous stable version.
These enhancements would greatly improve the usability of custom app extensions in Flow by reducing manual intervention and providing more flexibility in version control.
Would love to hear thoughts from the Shopify team and the community on this!
In reference to those docs, when deploying a new version of a trigger or action, existing workflows are not automatically updated to use the new version of the trigger and action. My feature request addresses the pain point caused by this.
Yeah, understand the need here. I think if you change a field on a trigger or action, it’s treated as a breaking change, where it only affects new uses of that trigger or action.
That is because breaking changes will break workflows. For example, if a workflow is relying on data from a trigger that changes or disappears, of if an action adds a new require field or changes how one of them works.
One solution to that would be for partners to write migrations for any changes.
For your specific issue, what changes were you making?
That makes sense - unfortunately, we are making changes to the runtime url defined in the extension.toml file. As of now, changing this attribute is not a breaking change.