Skip to content

Version pinning GA release #10676

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
OlufunkeMoronfolu wants to merge 2 commits into from
Closed

Version pinning GA release #10676

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cae6144
Version pinning GA release
OlufunkeMoronfolu Jan 29, 2026
2122b46
Add K8s distinction
OlufunkeMoronfolu Jan 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions content/en/docs/deployment/mendix-cloud-deploy/version-pinning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,11 @@ description: "Version Pinning guarantees consistent platform configurations acro
# The anchors in this document are referenced from other documents. Do NOT remove!
---

{{% alert color="warning" %}}
This feature is in Limited Availability. For more information, see [Release Status](/releasenotes/release-status/#limited-availability).
{{% /alert %}}

## Introduction

Mendix Cloud(Kubernetes) provides version pinning to guarantee consistent and predictable application behavior across all environments. For example, when you promote a Mendix application from acceptance to production, version pinning ensures that the same underlying platform configuration is reused across both environments. This configuration includes components critical to how your application runs in Mendix Cloud, such as runtime images, buildpacks, and supporting services, all of which remain identical across environments.
Mendix Cloud(Kubernetes) provides version pinning to guarantee consistent and predictable application behavior across all environments. For example, when you promote a Mendix application from acceptance to production, version pinning ensures that the same underlying platform configuration is reused across both environments.

This configuration includes components critical to how your application runs in Mendix Cloud, such as runtime images, buildpacks, and supporting services, all of which remain identical across environments.

By maintaining a consistent runtime stack, version pinning effectively eliminates subtle environmental differences, leading to more reliable and predictable application behavior throughout your development and deployment landscape.

Expand All @@ -26,8 +24,7 @@ This feature is only applicable to promotions between environments on Mendix Clo

You must meet the following conditions to use version pinning:

* **Company-level enablement** – Version Pinning must first be enabled at the company-level.
* **Mendix Cloud (Kubernetes) environment** – Your Mendix applications must be deployed to and running within environments hosted on Mendix Cloud (Kubernetes)
* **Mendix Cloud(Kubernetes) environment** – Your Mendix applications must be deployed to and running within environments hosted on Mendix Cloud (Kubernetes)
* **Environment promotion** – You must be promoting an application from one environment to another (for example from test to acceptance, or acceptance to production).
* **Same application, same company** – Both the source and target environments must belong to the same application within the same company.

Expand Down
6 changes: 3 additions & 3 deletions content/en/docs/releasenotes/deployment/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ Follow the links in the table below to see the release notes you want:

| Type of Deployment | Last Updated |
| --- | --- |
| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | January 18, 2026 |
| [Mendix on Kubernetes](/releasenotes/developer-portal/mendix-for-private-cloud/) | January 8, 2026 |
| [Mendix on Azure](/releasenotes/developer-portal/mendix-on-azure/) | January 8, 2026 |
| [Mendix Cloud](/releasenotes/developer-portal/mendix-cloud/) | February 4, 2026 |
| [Mendix on Kubernetes](/releasenotes/developer-portal/mendix-for-private-cloud/) | January 26, 2026 |
| [Mendix on Azure](/releasenotes/developer-portal/mendix-on-azure/) | January 22, 2026 |
| [SAP Business Technology Platform (SAP BTP)](/releasenotes/developer-portal/sap-cloud-platform/) | September 28, 2025 |
| [Other Deployment Options](/releasenotes/developer-portal/on-premises/) | September 15, 2023 |

Expand Down
8 changes: 8 additions & 0 deletions content/en/docs/releasenotes/deployment/mendix-cloud/2026.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,14 @@ description: "2026 Release notes for Mendix Cloud"
weight: 1
---

## February 2026

### February 4, 2026

#### General Availability Release

* [Version Pinning](/developerportal/deploy/version-pinning/) is now in general availability (GA) and enabled by default for all Mendix Cloud(Kubernetes) users.

## January 2026

### January 18, 2026
Expand Down
2 changes: 1 addition & 1 deletion layouts/partials/landingpage/latest-releases.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ <h4 class="lp-panel-title">Latest Releases</h4>
</li>
<li class="lp-panel-list">
<a href="/releasenotes/developer-portal/deployment/">Deployment</a>
<p class="rn-date">January 18, 2026</p>
<p class="rn-date">February 4, 2026</p>
</li>
<li class="lp-panel-list">
<a href="/releasenotes/catalog/">Catalog Release 2.150.0</a>
Expand Down