Skip to content
This repository was archived by the owner on Dec 29, 2025. It is now read-only.

Commit 9895af4

Browse files
author
GitHub Actions
committed
Added release notes and version entries for 2025.50.0
1 parent 1bdda51 commit 9895af4

File tree

1 file changed

+181
-0
lines changed

1 file changed

+181
-0
lines changed

blog/2025-11-19-Release-0.md

Lines changed: 181 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,181 @@
1+
---
2+
author: meshcloud
3+
title: Release 2025.50.0
4+
---
5+
6+
Release period: 2025-11-12 to 2025-11-19
7+
8+
This release includes the following issues:
9+
* Communication Emails Use Correct Subject
10+
* Fixed Issue Preventing Workspace Members From Adding Tenant Services
11+
* New meshPlatformType API for Custom Platform Types
12+
* Tag Validation for meshObject API Rollout Notice
13+
* Fix Double Encryption in Building Block Creation Via API
14+
* Event Logs for Payment Methods
15+
* Landing Zone Quotas are Now Available in the meshLandingZone API
16+
* Communication Center Now Part of Developer Portal Module
17+
* New Event Log Viewer Role for Read-Only Access to Event Logs
18+
* Fix Capitalization of meshStack in Page Titles
19+
* Fix Issue with User Bindings on Workspaces
20+
* Extend Admin Permissions on meshObject API
21+
* Building Block Runner Selection in Panel
22+
* Fix Metering Status Display After Platform Configuration Save
23+
* Streamlined User Access Editing with Modal Dialog
24+
<!--truncate-->
25+
26+
## Ticket Details
27+
### Communication Emails Use Correct Subject
28+
**Audience:** User<br>
29+
30+
#### Description
31+
Fixed an issue where communication emails were not using the provided subject. Previously,
32+
the system would always use the default subject, ignoring any custom subject. Now, if a custom subject is provided, it
33+
will be used instead of the default subject.
34+
35+
### Fixed Issue Preventing Workspace Members From Adding Tenant Services
36+
**Audience:** User<br>
37+
38+
#### Description
39+
We fixed an issue that could prevent workspace members from adding a service to a tenant they have access to. Workspace
40+
members can now add and configure tenant-level building blocks as intended, enabling proper self-service access to
41+
marketplace services for their tenants.
42+
43+
### New meshPlatformType API for Custom Platform Types
44+
**Audience:** User<br>
45+
46+
#### Description
47+
The meshPlatformType API lets you manage custom platform types programmatically. This enables you to integrate
48+
proprietary or emerging cloud platforms beyond meshStack's built-in types (AWS, Azure, GCP, etc.). You can create,
49+
read, update, list, and deactivate custom platform types via the API.
50+
51+
#### How to use
52+
All API keys can read platform types. Creating custom platform types requires platform save permission.
53+
Updating and deactivating them requires admin permissions. When you deactivate a platform type, existing platforms
54+
continue to work, but new platform instances of this type cannot be created.
55+
56+
### Tag Validation for meshObject API Rollout Notice
57+
**Audience:** User<br>
58+
59+
#### Description
60+
We are rolling out an important update to meshObject API tag validation behavior for admin permissions. Unless
61+
already manually configured, existing meshStacks now default to the legacy tag validation bypass behavior to
62+
preserve backward compatibility. Starting April 1st, 2026, all meshStacks must enforce full tag validation and the
63+
legacy bypass setting will no longer be available.
64+
65+
#### How to use
66+
Please review the [deprecation notice](https://feedback.meshcloud.io/deprecations/p/deprecation-bypassing-tag-validation-in-admin-api-calls)
67+
for more details on this change and its implications.
68+
We recommend reviewing your API integrations and disabling the bypass in the Partner Area under Settings >
69+
Compliance > Tags once you've confirmed your integrations supply valid meshObjects that pass your configured tag
70+
validation rules. You must disable the legacy tag validation bypass before April 1st, 2026. After that date, all
71+
meshStacks will enforce full tag validation for admin API operations.
72+
73+
### Fix Double Encryption in Building Block Creation Via API
74+
**Audience:** User<br>
75+
76+
#### Description
77+
When creating Building Blocks via the meshObject API with sensitive static inputs defined on the Building Block Definition,
78+
these inputs were being encrypted twice. This caused Building Block runs to fail because the double-encrypted values could
79+
not be properly decrypted by the Building Block runner. This issue has been fixed.
80+
Failed Building Blocks will be repaired by starting new runs.
81+
82+
### Event Logs for Payment Methods
83+
**Audience:** User<br>
84+
85+
#### Description
86+
We now create event logs for payment methods. When you create, modify, or delete a payment method, these changes
87+
are now visible in the Event Logs section in the admin area. This provides you with better visibility and
88+
auditability of payment method changes in your meshStack installation.
89+
90+
### Landing Zone Quotas are Now Available in the meshLandingZone API
91+
**Audience:** User<br>
92+
93+
#### Description
94+
The meshLandingZone preview API now exposes quotas configured for landing zones. This allows you to retrieve and
95+
set resource limits (such as CPU cores and memory) for landing zones via the meshObject API. Quotas define resource
96+
limits that will be applied to tenants using a specific landing zone.
97+
98+
#### How to use
99+
When creating or retrieving a landing zone via the meshLandingZone API, the `spec.quotas` field now contains an
100+
array of quota entries. Each entry has a `key` (the quota name) and `value` (the quota limit). For example, a
101+
landing zone might specify `cpu: 10` cores and `memory: 20` GB.
102+
103+
Quota support is currently available for Kubernetes, OpenShift, Azure Kubernetes Service (AKS), Cloud Foundry and
104+
OpenStack platforms. For platforms that do not support quotas (such as AWS, GCP, and Azure), the quotas field will
105+
be an empty array.
106+
107+
### Communication Center Now Part of Developer Portal Module
108+
**Audience:** User<br>
109+
110+
#### Description
111+
We have simplified our product modules by consolidating the Communication Center into the Developer Portal module.
112+
Previously, the Communication Center was split between a "light" version in the Developer Portal and a "full" version
113+
in the separate Developer Engagement module. Now, all Communication Center features are available to all customers
114+
with the Developer Portal module enabled.
115+
116+
#### How to use
117+
If you previously had the Developer Portal module enabled, you can now access all Communication Center features
118+
without needing a separate Developer Engagement module license. This includes creating communications with action
119+
required type, filtering by building blocks, workspace tags, and building block tags. No configuration changes are
120+
required on your part.
121+
122+
### New Event Log Viewer Role for Read-Only Access to Event Logs
123+
**Audience:** User<br>
124+
125+
#### Description
126+
A new "Auditor" role is now available in the Admin Area. This role allows you to grant users read-only
127+
access to event logs for audit purposes without providing full administrative permissions. Users with this role can
128+
view all event log entries across workspaces but cannot modify any settings or perform other administrative actions.
129+
130+
### Fix Capitalization of meshStack in Page Titles
131+
**Audience:** User<br>
132+
133+
#### Description
134+
We corrected the capitalization of "meshStack" in browser page titles across the entire application. Previously, some
135+
page titles used lowercase "meshstack", which has been updated to use the proper capitalization.
136+
It also adds german translations for previously missed page titles.
137+
138+
### Fix Issue with User Bindings on Workspaces
139+
**Audience:** User<br>
140+
141+
#### Description
142+
We resolved a bug that prevented users to be assigned to workspaces correctly.
143+
This was the case when SCIM was disabled, user invitation tokens were disabled as well and
144+
an identity lookup was configured for your meshStack.
145+
146+
### Extend Admin Permissions on meshObject API
147+
**Audience:** User<br>
148+
149+
#### Description
150+
We elevated the admin permissions so they now enable management
151+
of meshObjects on the partner workspace as well. This includes
152+
e.g. the management of meshPlatforms.
153+
154+
### Building Block Runner Selection in Panel
155+
**Audience:** User<br>
156+
157+
#### Description
158+
Platform engineers can now select the building block runner for their building block definition version directly in
159+
the panel when creating or editing a building block definition. Previously, meshStack automatically selected an
160+
appropriate runner based on the implementation type. This manual selection allows you to choose between shared
161+
runners provided by meshStack and dedicated runners hosted by your workspace for additional control and flexibility.
162+
163+
### Fix Metering Status Display After Platform Configuration Save
164+
**Audience:** User<br>
165+
166+
#### Description
167+
We fixed an issue where the metering configuration status was not properly updated in the meshPanel after
168+
saving platform configuration changes. Previously, the status would not reflect the current state until
169+
the page was refreshed.
170+
171+
### Streamlined User Access Editing with Modal Dialog
172+
**Audience:** User<br>
173+
174+
#### Description
175+
We improved the user experience when editing access permissions for workspaces and projects
176+
in the new access control interface (access control v2). Instead of navigating to a separate
177+
page, you can now edit user access directly in a modal dialog that opens on the same screen.
178+
179+
Note: This change only affects customers who have access to the new access control v2 feature.
180+
If you are using the standard access control interface, this change does not apply to you.
181+

0 commit comments

Comments
 (0)