Skip to Content

Changes for page 268 - Underlying Update

Last modified by Erik Bakker on 2026/05/18 16:45
From version 185.1
edited by CarlijnKokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version
To version 334.1
edited by Erik Bakker
on 2026/05/18 11:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +268 - Underlying Update
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,27 +1,19 @@
1 -In the last sprint cycle, we focused on ....
1 +This release includes significant improvements regarding our internal platforms. This includes improvements in the DSH proxy certifcate rotation process. On top of that, it introduces a new version of Mendix on which we are running and various updates on underlying libaries. Subsequently, we have introduced a fix for the stability of our documentation platform. Enjoy reading our latest updates on the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.268 - Underlying Update.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Minor Changes ====
6 6  
7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
7 +* General - Event Streaming: Various updates regarding the proxy certificate rotation process.
8 +** Proxy certificates must always be valid in DSH so clients do not face any issues. A schedule event runs daily during working hours to verify this.
9 +** If certificate rotation fails in the test environment, it will not continue to ACCP and PROD
10 +* General - Feedback Functionality: Updated the feedback functionality. Although this changes the user process it should allow you to provide more elaborated feedback.
9 9  
10 -=====Minor changes=====
12 +==== Bug fixes ====
11 11  
12 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 -* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 -* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 -* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
14 +* General - User Access Control: While users are being deactivated, they are also being removed from the models unless they are the contact person for the model. (#943)
15 +* Create - Documentation Portal: A stability improvement will be rolled out for our documentation website.
18 18  
19 -====Bug fixes====
17 +==== Remarks ====
20 20  
21 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22 -* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23 -* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26 -
27 -
19 +* Upgraded our main application to Mendix 10