Merge remote-tracking branch 'upstream/development' into development

Author: github-actions[bot]

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md

@@ -156,9 +156,9 @@ The AWS S3 library is also updated in the latest LTS versions of Studio Pro:
 
 Mendix Operator 2.25 (or later versions) will automatically recognise an S3 bucket's region from its endpoint address:
 
-* If the bucket endpoint has a `<subdomains>.<region>.amazonaws.com` format (or `<subdomains>.<region>.amazonaws.com.<suffix>` format for AWS China regions),
-the Operator uses `<region>` as the S3 region name.
-* If the S3 bucket endpoint does not match this format, the Mendix Operator will use a default `us-east-1` region, as this works with most S3-compatible buckets like [Minio](#blob-minio) and [Google Cloud Storage](#blob-gcp-storage-bucket).
+* If the bucket endpoint has a `<subdomains>.<region>.amazonaws.com` format (or `<subdomains>.<region>.amazonaws.com.<suffix>` format for AWS China regions), the Operator uses `<region>` as the S3 region name.
+* For buckets that use the `<bucketname>.s3.amazonaws.com` [Legacy global endpoint](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#VirtualHostingBackwardsCompatibility) format, Mendix Operator 2.26.1 (or later versions) detects the bucket region with a [HeadBucket call](https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html#API_HeadBucket_ResponseSyntax). If the call fails, the Mendix Operator uses the default `us-east-1` region instead.
+* If the S3 bucket endpoint does not match this format, the Mendix Operator uses a default `us-east-1` region, as this works with most S3-compatible buckets (for example, [Minio](#blob-minio) and [Google Cloud Storage](#blob-gcp-storage-bucket)).
 
 In some scenarios (legacy or custom S3 endpoints), this autodetection might not work correctly. In this case, you can manually specify the S3 bucket region by setting the [com.mendix.storage.s3.Region](/refguide/custom-settings/#commendixstorages3Region) Custom Runtime Setting. A manually specified `com.mendix.storage.s3.Region` will override the autodetected bucket region.
 

content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md

@@ -36,8 +36,8 @@ If deploying to Red Hat OpenShift, you need to specify that specifically when cr
 
 Mendix on Kubernetes Operator `v2.*.*` is the latest version which officially supports:
 
-* Kubernetes versions 1.19 through 1.34
-* OpenShift 4.6 through 4.20
+* Kubernetes versions 1.19 through 1.35
+* OpenShift 4.6 through 4.21
 
 {{% alert color="warning" %}}
 Kubernetes 1.22 is a [new release](https://kubernetes.io/blog/2021/08/04/kubernetes-1-22-release-announcement/) which removes support for several deprecated APIs and features.

content/en/docs/marketplace/platform-supported-content/modules/global-inbox.md

@@ -139,5 +139,5 @@ Any user that can see a task in Publisher Application can see the same task in t
 ## Limitations
 
 * **Global Inbox** does not support [Workflow Groups](/refguide/workflow-groups/) at the moment. This will be introduced at a later stage.
-* The beta version of **Global Inbox** has limited support for error handling. Any exceptions that occur in a microflow after updating a user task (or other Workflow-related entity) in the same microflow (for example, updating the targeted users or due date) might result in data becoming out of sync. This is a temporary limitation that will be resolved in an upcoming version.
+* **Global Inbox** has limited support for error handling. Any exceptions that occur in a microflow after updating a user task (or other Workflow-related entity) in the same microflow (for example, updating the targeted users or due date) might result in data becoming out of sync. This is a temporary limitation that will be resolved in an upcoming version.
 * Workflows and tasks that are modeled in the same app that includes the Global Inbox module are NOT available in the Global Inbox. The Global Inbox app only consumes and displays workflow instances from other Mendix applications.

content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md

@@ -28,6 +28,14 @@ The Mendix Data Loader is covered under the Mendix EULA. While the loader itself
 
 Depending on your use case, your deployment environment, and the type of app that you want to build, you may also need a license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/).
 
+### Mendix Data Loader Enterprise Edition
+
+For our enterprise customers who require advanced integration and administration capabilities, we offer the Mendix Data Loader Enterprise Edition. This specialized edition is designed for large-scale operations and focuses on synchronizing data from your Mendix applications. It features a headless API, implemented as Snowflake stored procedures, allowing for programmatic invocation. This enables bulk administration of Mendix applications for synchronization or seamless integration with self-service portals. Furthermore, the Enterprise Edition is ideal for customers who require complete control over Snowflake security objects, such as network rules, external access integration, and secrets, ensuring alignment with their stringent security policies.
+
+Because of its advanced nature and because it requires knowledge of Snowflake administration to set up and use its headless API, the Enterprise Edition is not publicly available on the Snowflake Marketplace. Instead, you can request it directly from Mendix. Upon request, we will engage with your team to understand your specific business case and validate if the Enterprise Edition aligns with your operational needs. If suitable, we will facilitate the deployment of the Enterprise Edition directly to your designated Snowflake accounts, and provide comprehensive additional documentation to support your implementation. This approach ensures that the Enterprise Edition is adopted by organizations that can fully benefit from its API-driven capabilities, while maintaining full control over their Snowflake environment.
+
+To request the Mendix Data Loader Enterprise Edition for Snowflake, contact us at [mendix-tech-alliance-dev-team.disw@siemens.com](mailto:mendix-tech-alliance-dev-team.disw@siemens.com).
+
 ## Installation
 
 Follow instructions in [Install an app from a listing](https://other-docs.snowflake.com/en/native-apps/consumer-installing) to add the component to your Snowflake environment.

content/en/docs/refguide/mobile/designing-mobile-user-interfaces/native-styling-element-guide.md

@@ -641,7 +641,7 @@ The default class to style all reference selector inputs is named `ReferenceSele
 
 Images, videos, and files help your user app manage images and other files. For more information on these widgets, see [Images, Videos, and Files](/refguide/image-and-file-widgets/).
 
-### Image (#new-image)
+### Image {#new-image}
 
 The image widget can be used to show a static or dynamic image or an icon on a page, layout, or snippet.
 

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -12,6 +12,18 @@ For information on the current status of deployment to Mendix on Kubernetes and
 
 ## 2026
 
+### April 9, 2026
+
+#### Mendix Operator v2.26.1 {#2.26.1}
+
+* We have improved the AWS S3 region detection for bucket endpoints using the [Legacy global endpoint](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#VirtualHostingBackwardsCompatibility) format.
+* We have updated components to use the latest dependency versions in order to improve security score ratings for container images.
+* We have updated the list of supported platforms to include Kubernetes 1.35 and OpenShift 4.21.
+
+#### License Manager CLI v0.10.9 {#0.10.9}
+
+* We have updated components to use the latest dependency versions in order to improve security score ratings for container images.
+
 ### April 2, 2026
 
 #### Portal Improvements

content/en/docs/releasenotes/feature-release-calendar/_index.md

@@ -30,7 +30,8 @@ General Availability means that a feature is available for all users. This type
 | Agent Observability | General Availability: Mx 11.5 + Mx 10.24 |
 | Model Agents as part of your Workflow | General Availability: Mx 11.9 |
 | Dynamic Case Management | Private Beta: Mx 11.3 <br/>Limited Availability: Mx 11.12 |
-| Global Inbox Workflow Tasks | Public Beta: Mx 11.9 <br/>General Availability: Mx 11.12 |
+| Global Inbox Workflow Tasks | General Availability: Mx 11.9 |
+| Global Inbox Other Tasks | General Availability: Mx 11.12 |
 | Workflow Non-interrupting Event Subprocesses (Message trigger) | Public Beta: Mx 11.8 <br/>General Availability: Mx 11.9 |
 | Workflow Interrupting Event Subprocesses (Message trigger) | General Availability: Mx 11.12 |
 | Workflow Interrupting Event Subprocesses (Timer trigger) | General Availability: Mx 11.12 |

content/en/docs/releasenotes/mendix-cloud-genai-resource-packs/_index.md

@@ -12,6 +12,12 @@ These release notes cover changes made to the [Mendix Cloud GenAI Resource Packs
 
 ## 2026
 
+### April 9, 2026
+
+#### New Features
+
+It is now possible to add external users to your resources, making collaboration across organizations easier.
+
 ### March 5, 2026
 
 #### Fixes

content/en/docs/releasenotes/studio-pro/11/11.9.md

@@ -159,6 +159,7 @@ We changed how Studio Pro stores Marketplace identity data for widgets. This dat
 * We fixed an issue where deleting a duplicate navigation profile deleted the wrong duplicate profile.
 * We fixed an issue where mxbuild incorrectly reported that the modern web client bundler stopped unexpectedly, while the React client bundler completed normally without errors.
 * We fixed an issue where an Oops pop-up window appeared when copying button widgets with parameter arguments to page templates or building blocks, and when creating page templates or building blocks from pages or widgets containing such buttons.
+* We fixed History Web pane timeouts for large repositories and eliminated refresh commit history errors
 
 ### Deprecations
 

content/en/docs/support/new-app-node-request-template.md

@@ -27,7 +27,7 @@ To deploy your app to a new licensed node, you will need to request a node from
 * **Mendix Cloud Dedicated** – Select this option for apps deployed to Mendix Cloud Dedicated.
 * **Mendix for Private Cloud** – Select this option for apps deployed to Kubernetes using the Mendix Operator. Refer to [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) for more information.
 * **Server-based (Windows Server)** – Select this option for apps deployed to Windows. You are required to enter the **Server ID**, which you can retrieve by following the steps in the [Windows Server](/developerportal/deploy/licensing-apps-outside-mxcloud/#windows-server) section of *Licensing Apps*.
-* **Container-based (Docker, Cloud Foundry, Kubernetes)** – Select this option for apps deployed to Docker, Cloud Foundry, or Kubernetes, without Mendix Operator.
+* **Container-based (Docker, Cloud Foundry, Kubernetes)** – Select this option for apps deployed to Portable App Distribution, Docker, Cloud Foundry, or Kubernetes, without Mendix Operator.
 * **SAP** – Select this option for apps deployed to SAP.
 
 To request your node from Mendix Support, complete the following steps: