Hello,
One of the strengths of open-source software is flexibility—giving users the ability to choose what works best for their specific needs and environments. While working with Mautic’s console-based upgrade process, I noticed an opportunity to improve that flexibility.
Currently, when upgrading Mautic via the console command, users are only given the option to fetch and install the latest available release. While this works well for many cases, it can be limiting for users who may prefer or require a specific minor version instead of the most recent one.
There are several valid reasons why an end user might not want to upgrade to the latest release immediately. For example, they may need to maintain compatibility with existing integrations, avoid newly introduced bugs, or follow internal testing and rollout procedures. In these scenarios, having the ability to select a specific version becomes essential.
A helpful enhancement would be to modify the upgrade command so that it retrieves and displays a list of available updates. From there, users could choose which version to install—perhaps by passing a version parameter, similar to how many other open-source tools handle version control during upgrades.
This approach would strike a balance between simplicity and control: users who want the latest version can still upgrade quickly, while those with more specific requirements gain the flexibility they need.
Introducing version selection into the upgrade workflow would make Mautic more adaptable and user-friendly, especially for teams managing production environments where stability and predictability are critical.
It would be great to see this feature considered in future updates.
Thanks