CloudHub Runtime Continuous Updates

MuleSoft regularly runs scans to identify security vulnerabilities in Mule runtime engine, JVM, and the underlying operating system, and then automatically applies security patches based on the following SLA:

Once per month, MuleSoft releases a date-patch update, which includes backward-compatible bug fixes to address any issues discovered in Mule runtime engine. The monthly date-patch update might include security patches if the scheduled date is within the security SLA.

The format of the version number for these updates is:

Major.Minor.Patch - Date

Here’s an example version number, including the patch date:

4.2.2 - 05-04-2020

The monthly patches update applications only to the latest date patch for the patch version. They do not change the patch version number.

Starting with Mule 4.5, MuleSoft introduces two new release channels, Edge and Long-term Support (LTS). The Mule runtime versioning schema for the new release channels is:

Major[numeric] . Minor[numeric] . Patch[numeric] : Build[numeric] Channel[e for edge, nothing for LTS]

Some examples of these values are: 4.5.0:1e for Edge, and 4.6.0:1 for LTS.

CloudHub uses kernel live patching in the underlying VMs to apply the latest security and critical bug patches to the OS. You do not have to restart the CloudHub application between the monthly patching cycles.

Starting with Mule 4.5, MuleSoft introduces two new release channels, Edge and Long-term Support (LTS). Both release channels are available in all our deployment models: Anypoint Runtime Fabric, CloudHub, CloudHub 2.0, and Hybrid Standalone. Consider the following factors to determine the approach that best suits your requirements ahead of the Mule 4.4 End of Standard Support.

In February, both Edge and LTS release with the same underlying version, including a minor Mule runtime version and new features.

To review the new support policy that aligns with the new release periods and types of releases, see MuleSoft Support Policy.

Starting with Mule 4.5, MuleSoft releases Edge versions in February, June, and October. Use the Edge channel if you want to stay on top of the latest features and feel comfortable with a more frequent release cycle and auto-app upgrade cycle. The Edge channel includes the latest features and innovations available on the MuleSoft platform.

Starting with Mule 4.6, MuleSoft releases Long-Term Support (LTS) versions annually in February. If you are on Mule 4.4, you are not required to upgrade to Mule 4.6. However, because Mule 4.5 releases in October 2023, Standard Support for Mule 4.4 ends in October 2024, followed by the End of Extended Support in October 2025.

For CloudHub and CloudHub 2.0 customers, once Standard Support for Mule 4.4 ends, if you want to deploy new apps, you must do so on Mule 4.6 LTS or Mule 4.8 Edge.

Use the LTS channel if you want to avoid maintaining new versions frequently. The LTS channel adopts new capabilities after they have been introduced via Edge releases.

You can switch from an Edge version to an LTS version and vice versa. However, when moving from Edge to LTS, you must choose a later LTS version. For example, if you choose Mule 4.6 LTS and you want to implement a specific new feature released on Mule 4.7 Edge, you can opt into that Edge release, then merge into Mule 4.9 LTS once it is available. MuleSoft does not support apps that are switched from Edge to an older LTS version. For example, switching an app from Mule 4.7 Edge to Mule 4.6 LTS might result in losing some of the new features in the older LTS version.

The following table shows the Mule runtime release cadence support for CloudHub:

Application lifecycle management depends on the deployment model.

The version naming convention depends on the deployment model you are using. A version increments:

Application lifecycle management depends on the deployment model.

The version naming convention depends on the deployment model you are using. A version increments:

The Update Available column indicates which apps require a runtime version update. You can schedule the update to occur at your convenience.

Before updating apps in the production environment, update them in the sandbox environment and run the required tests.

When a new runtime version is available:

MuleSoft applies the updates automatically, based on the published schedules. If you want, you can update them manually at your convenience.

Zero-downtime restarts don’t work in the following cases:

If either case applies to your application, contact Support and your CSM account representative for information about updating the application to be cloud-ready.

After a new update occurs, you can check your applications status state in the Status column in Runtime Manager’s Applications tab.

You can also check your application logs to verify if your application was deployed correctly and take any remediation actions in the event of some auto-minor update-related issue. For more information, visit View Logs.

To be notified by e-mail when an error occurs after an automated update, you can create an alert.

With blue-green deployments, when an automated update fails to be deployed to a new worker, the application continues to run the non-latest patch version on the currently running worker.

Possible failure reasons include but are not limited to:

If an application fails to be automatically updated after two monthly patching cycles, the application is stopped and force updated to the latest patch version. Applications that fail to start require your action to address patches.