Skip to content

Commit 26e0c61

Browse files
author
GitHub Actions
committed
Added release notes and version entries for 2025.24.0
1 parent 5cc8bba commit 26e0c61

File tree

1 file changed

+81
-0
lines changed

1 file changed

+81
-0
lines changed

website/blog/2025-06-11-Release-0.md

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
author: meshcloud
3+
title: Release 2025.24.0
4+
---
5+
6+
Release period: 2025-06-04 to 2025-06-11
7+
8+
This release includes the following issues:
9+
* Building Block Definition Input Form Improvements
10+
* Partial Role Mappings Now Allowed in Landing Zones
11+
* Building Block Definition Inputs Form Improvement
12+
* Fixed Email Type Label
13+
* Building Block input type modification support
14+
* Project Role Policies
15+
* Improvement for Building Block Definition Import
16+
* Building Block Definition Import Improvement
17+
<!--truncate-->
18+
19+
## Ticket Details
20+
### Building Block Definition Input Form Improvements
21+
**Audience:** User, Partner, Operator<br>
22+
23+
#### Description
24+
We fixed a typing issue with the building block definition inputs
25+
form that occasionally occurred e.g. in case strings were used
26+
that contain only digits.
27+
28+
### Partial Role Mappings Now Allowed in Landing Zones
29+
**Audience:** Partner<br>
30+
31+
#### Description
32+
Before, all role mappings from project roles to platform roles had to be specified within a landing zone.
33+
Now, you can decide to omit one or more mappings. If a mapping is missing, users with that project role
34+
will not be replicated, and platform groups relying on those mappings won't be created.
35+
36+
### Building Block Definition Inputs Form Improvement
37+
**Audience:** User, Partner, Operator<br>
38+
39+
#### Description
40+
We improved the form on the tab for building block definition version input editing
41+
in the panel.
42+
The button for automatic generation of cloud provider credentials now works as expected.
43+
Also, we removed a bug that would occasionally occur when editing multiple inputs at the same time.
44+
45+
### Fixed Email Type Label
46+
**Audience:** User<br>
47+
48+
#### Description
49+
Previously, the email type was always displayed as "string" in the tag overview. This has been updated to "email" to more accurately represent the nature of the data.
50+
51+
### Building Block input type modification support
52+
**Audience:** User<br>
53+
54+
#### Description
55+
You can now modify the input type of Building Block definition inputs in draft versions. This enables you to change
56+
input types from string to integer, boolean, or other supported types when creating new versions of your Building
57+
Block definitions.
58+
59+
### Project Role Policies
60+
**Audience:** User<br>
61+
62+
#### Description
63+
We introduced policies on project roles. Now you can define which users/groups can be assigned to which project roles.
64+
This is useful for ensuring that only authorized users/groups can access certain roles within a project, enhancing security and compliance.
65+
66+
### Improvement for Building Block Definition Import
67+
**Audience:** User, Partner, Operator<br>
68+
69+
#### Description
70+
We improved the import functionality when you add building block definitions
71+
from meshStack Hub to your meshStack. More specifically, numeric values are
72+
now parsed correctly without trailing zero decimals.
73+
74+
### Building Block Definition Import Improvement
75+
**Audience:** User, Partner, Operator<br>
76+
77+
#### Description
78+
We resolved an issue that would allow users to import
79+
building block definitions to workspaces they do
80+
not have sufficient permissions for.
81+

0 commit comments

Comments
 (0)