---
schema_version: "1"
id: b90606dfae39492a92bb120358b91bb04df88a4d687b524e8bd662111d2b32d0
title: Update Patches to Mule
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/mule-runtime/patching-mule-versions.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions
source_site: docs.mulesoft.com
content_type: documentation
content_hash: b47d0eff39e444435fc259e8a097b9166977a0c93612619a7a68a4ce92722b48
description: MuleSoft Documentation Site
latest: true
---
# Update Patches to Mule

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.

A patch update version appends an update identifier such as `-20210622` to the release version, for example, `4.3.0-20210622` for the Mule 4.3.0 release. You can find release notes for monthly Mule runtime engine patch updates in [MuleSoft Release Note Summary by Month](https://docs.mulesoft.com/jp/release-notes/quick-refs/by-date-index).

For Mule 4.5 and later, the version naming convention for CloudHub, CloudHub 2.0, and Runtime Fabric changes following the schema for the new release channels, Edge and Long-term Support (LTS).

_Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\] : Build\[numeric\] Channel\[e for edge, nothing for LTS\]_

Here are examples of the version numbers:

- Edge: 4.5.0:1e
- Edge: 4.6.0:1e
- LTS: 4.6.0:1

In the case of Standalone (On-Premises), the Mule runtime versioning changes from date-based, for example, `4.4.0-20230317` to semVer as:

_Major\[numeric\] . Minor\[numeric\] . Patch\[numeric\]_

Here are examples of the version numbers:

- 4.5.1
- 4.5.2
- 4.5.3

See [Edge and LTS Releases for Mule](https://docs.mulesoft.com/jp/release-notes/mule-runtime/lts-edge-release-cadence).

## [](#schedule)Patch Update Schedule

### [](#for-mule-4-5-and-later-versions)For Mule 4.5 and Later Versions

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.

Release cadence refers to new Mule runtime versions. Patch updates for supported versions continue to follow the monthly patch update schedule.

Consider these factors to determine the approach that best suits your requirements ahead of the Mule 4.4 End of Standard Support.

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 25%;">
<col style="width: 25%;">
<col style="width: 25%;">
<col style="width: 25%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">Channel Type</th>
<th class="tableblock halign-left valign-top">Release Cadence</th>
<th class="tableblock halign-left valign-top">Differentiators</th>
<th class="tableblock halign-left valign-top">Support Coverage</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Edge</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Up to three times per year</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="ulist">
<ul>
<li>
<p>Includes new features on a frequent release cadence with shorter maintenance coverage.</p>
</li>
<li>
<p>Versions aren’t FedRAMP approved.</p>
</li>
</ul>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>For versions 4.9 and later:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Standard Support until one month after the next Edge version is released</p>
</li>
<li>
<p>3 months of Extended Support</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>For version 4.8:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>5 months of Standard Support</p>
</li>
<li>
<p>3 months of Extended Support</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>For versions 4.5 to 4.7:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>4 months of Standard Support</p>
</li>
<li>
<p>4 months of Extended Support</p>
</li>
</ul>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>LTS</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Periodic (Scheduled for February)</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="ulist">
<ul>
<li>
<p>Includes new features introduced in prior Edge releases, along with new features introduced in the February Edge release. This release is maintained for an extended period over being the first to adopt new capabilities.</p>
</li>
</ul>
</div></div></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>For version 4.6 and later:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>A minimum of 18 months of Standard Support</p>
</li>
<li>
<p>A minimum of 6 months of Extended Support</p>
</li>
</ul>
</div></div></td>
</tr>
</tbody>
</table>

If an LTS version is released in February, both Edge and LTS share the same underlying version, including the same minor Mule runtime version and new features.

### [](#for-mule-4-4-and-previous-versions)For Mule 4.4. and Previous Versions

Each month, MuleSoft releases updates to selected Mule patch releases. In some cases, MuleSoft also releases updates outside of this timeframe, typically to expedite the delivery of more critical security updates.

Update strategies differ by product.

<table class="tableblock frame-all grid-all stretch">
<colgroup>
<col style="width: 42.8571%;">
<col style="width: 14.2857%;">
<col style="width: 28.5714%;">
<col style="width: 14.2858%;">
</colgroup>
<thead>
<tr>
<th class="tableblock halign-left valign-top">&nbsp;</th>
<th class="tableblock halign-left valign-top">On-premises (Standalone) Mule</th>
<th class="tableblock halign-left valign-top">CloudHub</th>
<th class="tableblock halign-left valign-top">Anypoint Runtime Fabric</th>
</tr>
</thead>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">On the first full week of the month, updates to Mule patches are available.
  MuleSoft provides updates only for patch versions that received bug fixes
  or security enhancements for the month.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Yes</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">You can continue to use a previous update to a Mule patch until the third
  full week of the month after the latest patch update is released.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Yes</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Your new deployments require use of the latest patch update during the third
  full week of the month.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">No</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Yes</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">On the third full week of the month, MuleSoft automatically updates existing
  applications to the latest patch update of Mule.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">No</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Yes</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Sandbox environments undergo forced updates Monday through Friday.</p>
</li>
<li>
<p>Production environments undergo forced updates Saturday and Sunday.</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>See the monthly update schedule in <a href="https://docs.mulesoft.com/jp/release-notes/cloudhub/cloudhub-runtimes-release-notes" class="xref page">CloudHub Runtime and Operating System Patch Update Release Notes</a>.</p>
</div></div></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">No<br>
<a href="https://docs.mulesoft.com/runtime-fabric/latest/runtime-patch-updates" class="xref page">Managing Mule Runtime Patch Updates for Runtime Fabric</a></p></td>
</tr>
</tbody>
</table>

On-premises Mule, CloudHub, and Anypoint Runtime Fabric updates for a given Mule patch version receive the same _Mule runtime engine_ fixes and enhancements. However, CloudHub and Anypoint Runtime Fabric patches can contain additional fixes and improvements that are specific to those products.

## [](#apply_patch_updates)Apply Patch Updates

Before updating the patch version on which you are running your Mule applications, review the [patch update schedule](#schedule).

The update procedure and schedule differ by deployment environment, whether on-premises, CloudHub, or Anypoint Runtime Fabric. To perform the update, see:

- [Mule Runtime Patch Updates for Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/runtime-patch-updates)
- [CloudHub Runtime Continuous Updates](https://docs.mulesoft.com/cloudhub/cloudhub-app-runtime-version-updates)
- [On-premise Mule Updates](#update_onprem_patch)

### [](#update_onprem_patch)Apply a Patch Update to an On-Premises (Standalone) Mule

For standalone Mule instances, which are hosted on-premises, you can use the [Mule Upgrade Tool](https://docs.mulesoft.com/mule-runtime/latest/mule-upgrade-tool) to automate the patching process or you can apply the patch manually to the instance.

MuleSoft typically releases monthly updates to the latest Mule minor versions and sometimes to earlier versions of Mule. Each Mule runtime patch update is posted to [Release Note Summary by Month](https://docs.mulesoft.com/jp/release-notes/quick-refs/by-date-index).

It is important to note that for on-premise deployments, a single instance of Mule can run one or more applications. When you patch an instance of Mule, the update applies simultaneously to all the applications deployed to that instance.

Standalone Mule installations do not undergo forced updates, but MuleSoft recommends that you apply the latest upgrades each month updates are available to benefit from the latest fixes and security enhancements.

For on-premises (standalone) Mule instances:

1. [Download Standalone Mule for On-Premises Deployments](#mule_standalone_download)

#### [](#mule_standalone_download)Download Standalone Mule for On-Premises Deployments

On the first full week of the month you can download new versions of updated Mule from your customer portal in the [Salesforce Help](https://help.salesforce.com).

The portal provides links to full Mule distributions that apply the latest patch:

- Installation files that follow the filename convention `mule-ee-distribution-standalone-x.y.z-YYYMMDD.zip` (for example,`mule-ee-distribution-standalone-4.3.0-20210622.zip`) are for new Mule installations, rather than updates to existing installations. These installations contain all fixes and enhancements up to the specified month and year.
    
    If you need to install a full instance of Mule instead of applying a patch update to an existing Mule instance, unzip the file, and set the `MULE` environment variable. For general guidance, see [Download, Install, Configure, and Upgrade On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task).