|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.7.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-02-12 to 2025-02-19 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Fix Workspace Creation for rare User Configuration |
| 10 | +* Filter Building Blocks via Definition UUID in API |
| 11 | +* Fix adding Validation Message on new Building Block Input |
| 12 | +* Fix known host not showing when provider name in URL |
| 13 | +* Fix Incorrect Data when Exporting Payment Methods via CSV |
| 14 | +* Cleanup Expired Role Bindings |
| 15 | +* Increased OSB platform restriction transparency |
| 16 | +* Remove Greeting from Email for Custom Recipients |
| 17 | +* Building Block Input and Output UI Improvement |
| 18 | +<!--truncate--> |
| 19 | + |
| 20 | +## Ticket Details |
| 21 | +### Fix Workspace Creation for rare User Configuration |
| 22 | +**Audience:** User<br> |
| 23 | + |
| 24 | +#### Description |
| 25 | +In rare cases, new users were unable to create workspaces in meshStack. This only affected users that |
| 26 | +had a special combination of user attributes. This issue has been fixed. |
| 27 | + |
| 28 | +### Filter Building Blocks via Definition UUID in API |
| 29 | +**Audience:** Customer, Partner<br> |
| 30 | + |
| 31 | +#### Description |
| 32 | +An additional query parameter was added to the building block API. You can now filter by building block definition UUID. |
| 33 | + |
| 34 | +### Fix adding Validation Message on new Building Block Input |
| 35 | +**Audience:** Customer, Partner<br> |
| 36 | + |
| 37 | +#### Description |
| 38 | +When adding a new building block definition input, the "Message on Regular Expression Failure" was not getting saved. |
| 39 | +Only when you set it again afterwards, it was saved as intended. This is fixed now. |
| 40 | + |
| 41 | +### Fix known host not showing when provider name in URL |
| 42 | +**Audience:** Operator<br> |
| 43 | + |
| 44 | +#### Description |
| 45 | +In the last release we introduced the functionality to hide the known host form for Terraform Building Blocks. |
| 46 | +The hiding also wrongfully occurred for repository URLs where the provider name was mentioned e.g. gitlab.company.com. |
| 47 | +This is now fixed and the known host form is available again in those cases. |
| 48 | + |
| 49 | +### Fix Incorrect Data when Exporting Payment Methods via CSV |
| 50 | +**Audience:** Partner, Customer<br> |
| 51 | + |
| 52 | +#### Description |
| 53 | +Previously, the Payment CSV export in the Admin Area under the Payment |
| 54 | +Methods page still used data from the old Chargeback process, even if |
| 55 | +Chargeback 2.0 was enabled. This has now been fixed, and it correctly exports |
| 56 | +the updated data. |
| 57 | + |
| 58 | +### Cleanup Expired Role Bindings |
| 59 | +**Audience:** Partner<br> |
| 60 | + |
| 61 | +#### Description |
| 62 | +Before, when a user was deleted in meshStack, their workspace role bindings were removed, but expired ones were |
| 63 | +accidentally skipped. Now, this has been fixed, and expired role bindings are deleted as well. |
| 64 | + |
| 65 | +### Increased OSB platform restriction transparency |
| 66 | +**Audience:** User<br> |
| 67 | + |
| 68 | +#### Description |
| 69 | +If an OSB platform was restricted to certain workspaces, the |
| 70 | +service instances screen was inaccessible without showing an error |
| 71 | +if your workspace was once part of the restriction but has been removed. |
| 72 | +We now have improved transparency and added information on what to do if |
| 73 | +the current workspace no longer has access to the OSB platform. |
| 74 | + |
| 75 | +### Remove Greeting from Email for Custom Recipients |
| 76 | +**Audience:** User<br> |
| 77 | + |
| 78 | +#### Description |
| 79 | +When providing a custom email address as a recipient for e.g. building block notifications, |
| 80 | +the greeting in the email was broken, as it only showed placeholders. This is fixed now and in those |
| 81 | +cases, no greeting is shown, as no name of the user is available to meshStack. |
| 82 | + |
| 83 | +### Building Block Input and Output UI Improvement |
| 84 | +**Audience:** User<br> |
| 85 | + |
| 86 | +#### Description |
| 87 | +In this release, we implemented a more streamlined and organized layout for Building Block input and output configurations. To this enhancement, |
| 88 | +a gap has been introduced between individual input and output sections, the deletion button has been moved from the header to the body of the input and output |
| 89 | +configuration for better visual flow and ease of access. |
| 90 | + |
0 commit comments