Runtime and Platform releases

Boomi updates the Boomi Enterprise Platform in official releases called the Runtime Release and Platform Release every other month. Refer to the Boomi status page to see the release schedule.

The Runtime Release includes all runtime updates and the Platform Release includes all Boomi Enterprise Platform updates. The following sections detail the differences between both types of releases and their release cadence.

Runtime Release

The Runtime Release is the official release of Boomi runtime features, enhancements, and fixes. It is a production quality release that provides the flexibility to apply updates to your runtimes, when it's most convenient for you, two weeks prior to the scheduled Platform release.

note

Updates to the user interface, the Boomi Enterprise Platform, Partner APIs, and any updates related to Flow and Boomi DataHub are not included in this release.

About the Runtime Release

The Runtime Release can include updates for the following runtimes:

Local, customer-hosted integration runtimes and runtime clouds
API gateways
Specific connectors

The Runtime Release typically occurs two weeks prior to the Platform Release date. Applying the Runtime Release is an optional action. You can apply available Runtime Release updates at any point between the Runtime Release and the Platform Release. If you choose not to apply the Runtime Release, you receive all runtime updates automatically on the Platform Release date, which typically occurs on the second Saturday of the release month.

After applying the Runtime Release to accounts automatically, all runtimes immediately restart and can require downtime. To avoid disrupting your processes and configurations at inconvenient times, you can use the Runtime Release up to two weeks sooner and perform the mandatory restart of runtimes as needed.

note

When applying the Runtime Release to a clustered runtime, including API Gateways, runtime clusters, and private clouds, the nodes will restart on a rolling basis to avoid downtime. For more information, see the topic Rolling restart of runtime clusters and clouds.

Monthly release notes, published at the start of the Runtime Release, list the updates that are or are not available in the Runtime Release. A list of upcoming Runtime Release dates are on the Notifications page. The Runtime Release does not include any features, enhancements, or fixes pertaining to the user interface, Boomi Enterprise Platform, or Platform API and Partner API updates.

You can optionally choose to apply Runtime Release updates at any time up until the next Platform Release. If you do not apply Runtime Release updates to your account before the next Platform Release, the updates are automatically applied when the next Platform Release occurs and your runtimes will require a restart.

Applying the Runtime Release

You can apply available Runtime Release updates to individual runtimes and Connectors via the Runtime & Connector Versions panel or using instructions in the Applying the Runtime and connector updates topic. You can also schedule automatic application of all runtime updates in bulk via the Runtime Release Scheduling panel, or following the instruction in the Scheduling release control updates topic.

Boomi-hosted Runtime updates

For Boomi hosted public and dedicated clouds, runtime updates are applied to test-class runtime clouds at the beginning of the Runtime Release period. Updates are applied to production-class runtime clouds as part of the Platform Release.

For managed clouds, the timing can be customized based on your preferences up to the Platform Release date.

Runtime Java Updates

Boomi provides quarterly Java updates for your runtimes to ensure the latest features, improvements, and security patches from the Amazon Corretto OpenJDK are available. These Java updates are applicable if you use the Boomi-provided Java instance (default, recommended). If you choose to configure your runtime to use an external Java instance, you are responsible for maintaining and patching that instance; the Boomi Java updates are not applicable.

The following is an overview of how these Java updates are managed for your runtimes:

The Java update is only available with the Platform release, so the update can be applied only after the Platform release happens. This ensures all runtimes have the latest runtime version to avoid compatibility issues with the Java update.
If your runtimes use a Boomi-managed Java instance, you have two options for applying the Java update:
- Manual - You can apply the update manually any time after the Platform release.
- Automatic - Alternatively, you can schedule your runtimes to apply Java updates automatically. Note that the first and last week options in the schedule are relative to the Platform release. Refer to Setting a schedule to update a runtime to the lastest Java version for more information. Note that this schedule is separate from the schedule to apply the Runtime Release.
The Java updates is applied to the runtime independently of the runtime version update. As a result, your runtimes will restart twice during the overall release cycle that includes a Java update: Once for the Runtime version update and again for the Java update.

The 2025 Java update schedule is as follows:

Quarter	Corretto Java update release date	Boomi Platform release date
Q1	January 15th	Boomi Platform March release
Q2	April 15	Boomi Platform July release
Q3	July 15	Boomi Platform September release
Q4	October 15	Boomi Platform January release (following year)

For more information on how to apply Java updates to your runtimes, see the Java Upgrade FAQ topic.

Questions and answers about Runtime Release

Is the Runtime Release considered a release candidate or beta release?

The Runtime Release is neither a beta release or a release candidate, but rather it is an official release. A release candidate (or beta release) is a version of the release that allows customers to test features and report defects, which are then prioritized and fixed in time for the full release. Report any issues related to the Runtime Release to Boomi Support. Boomi fixes issues as part of the regular development cycle for inclusion in a future release.

How can I know what features and fixes are or are not available in the Runtime Release?

With each Runtime Release, Boomi provides release notes that list the features and fixes included in Boomi's Runtime Release.

How do I know when updates are available prior to the Platform Release?

A system message appears in Integration when Runtime Release updates are available. You also can check the Runtime & Connector Versions panel in the Integration service, or the Gateway version panel in the API Management service to see if pending updates are listed for the respective runtimes. See the Applying the Runtime Release section of this topic for more information.

Additionally, the Runtime Release schedule is also posted on the Notifications page.

Who is able to apply the Runtime Release updates?

To apply updates to basic runtimes, runtime clusters, or runtime clouds, users with the Runtime Management privilege (typically users with the Administrator role) can apply the Runtime Release. You also must be authorized to update the selected runtime. You cannot apply updates to a runtime that you do not own, for example, a Boomi runtime cloud.

To apply updates to API Gateways, users with the API Management privilege (typically users with the Administrator role) can apply the Runtime Release.

If I have multiple runtimes, do I have to update all of them at the same time?

No, you do not have to update all of your runtimes at once. Instead, you can individually update any basic runtime, runtime cluster, runtime cloud, or API Gateway, as needed. See the section Applying the Runtime Release of this topic for more details.

Will the runtimes be updated or rolled back immediately after I click the button to apply or to rollback updates?

The request is sent to the runtime immediately. Allow time for the updates or rollback to take effect. The runtime may restart during this process. It waits for a period of inactivity before applying the updates or rollback.

Can people use the Platform while I apply the updates or a rollback?

Yes, users who are logged into the platform are not affected.

Can updates be applied to or rolled back on a runtime that is not currently running?

No, the updates or rollback are applied to the runtime the next time it starts.

What happens if I don’t apply the Runtime Release updates prior to the Platform Release?

On the Platform Release date, accounts are automatically updated to use the Runtime Release and Platform Release updates.

Can I opt out of applying a release update to my runtimes or the Platform?

No. Runtime and Platform updates are not optional. If you do not apply the Runtime Release during the two week period, it will be automatically applied along with the Platform Release on the Platform Release date.

Platform Release

The Platform Release delivers new features, enhancements, and fixes that pertain to each of the services that Boomi offers (Integration, Flow, API Management, and so on) and makes them generally available to users. The Platform Release includes updates related to the user interface, the Boomi Enterprise Platform, and API and Partner APIs.

The Platform Release typically occurs on the second Saturday of each month, though timing varies based on major holidays. Upcoming Platform Release dates are listed on the Notifications page. Release notes announce all upcoming updates at least two weeks prior to the scheduled release date.

When the Platform Release occurs, if you did not apply the updates in the most recent Runtime Release to your account, the updates are automatically applied.