Mule Upgrades and Patch Updates

Mule follows semantic versioning to denote major, minor, and patch releases. The version is specific to Mule applications that you deploy on-premises, to CloudHub through Anypoint Runtime Manager, or to Anypoint Runtime Fabric.

Patch updates are cumulative releases that include the latest bug fixes and security enhancements to a specific patch (x.y.z) version, plus all previously released features and fixes for that patch version. For updates, see Update Patches to Mule.

Unlike the patch update process, the Mule upgrade process is for upgrading to a later version. For example, you can upgrade from Mule 4.x to 4.y (such as 4.3.0 to 4.4.0) or Mule 4.x.y to 4.x.z (such as 4.2.1 to 4.2.2). For minor and patch version upgrades or a major version migration, see:

Though Mule guarantees compatibility with new minor, patch, or patch update versions, it is important to validate that your applications continue to run as expected in a testing environment before running them in a production environment.

Run your MUnit tests on any new version of Mule to validate the application’s behavior with that version.

The Mule upgrade tool provides an automated solution for updating and upgrading standalone on-premise instances of Mule runtime engine running version 4.1.5 or later. The tool is a command line utility that is available as a separate download, which enables you to integrate it with existing automated processes or workflows by using scripts and cron jobs.

See Mule Upgrade Tool for configuration and usage instructions.