|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.23.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-05-28 to 2025-06-04 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Add new meshPaymentMethod endpoints in meshObject API |
| 10 | +* Improved building block grid view |
| 11 | +* Add API Key permissions for meshPaymentMethods |
| 12 | +* Renamed Access Tabs for Improved Clarity |
| 13 | +* Better Error Message For Block Runs With Missing Outputs |
| 14 | +* Empty Building Block Selection on Azure Landing Zone |
| 15 | +* Keyboard Accessible Card Toggles |
| 16 | +* Fix Step Title of Building Block Run |
| 17 | +* README now correctly persisted |
| 18 | +* Fixed Broken Link in Project Access View |
| 19 | +* Fixed Building Block Default Input Number |
| 20 | +* Fixed Saving Landing Zone |
| 21 | +* Unmanaged Tenants tab title |
| 22 | +* Fixed Blank Page on General Tab Switch |
| 23 | +* Better Building Block Environment Variable Description |
| 24 | +<!--truncate--> |
| 25 | + |
| 26 | +## Ticket Details |
| 27 | +### Add new meshPaymentMethod endpoints in meshObject API |
| 28 | +**Audience:** User<br> |
| 29 | + |
| 30 | +#### Description |
| 31 | +This release introduces POST, PUT and DELETE method support for meshPaymentMethod objects via the meshObject API |
| 32 | +Platform teams and automation can now manage payment methods programmatically, enabling better integration and automation scenarios. |
| 33 | + |
| 34 | +#### How to use |
| 35 | +To use the new endpoints, refer to the meshObject API documentation for details on how to create, update, and delete |
| 36 | +meshPaymentMethod objects. This release introduces new permissions for API Keys, allowing you to control access |
| 37 | +to these endpoints. Permissions for creating, updating and deleting payment methods can only be assigned by admins. |
| 38 | + |
| 39 | +### Improved building block grid view |
| 40 | +**Audience:** User<br> |
| 41 | + |
| 42 | +#### Description |
| 43 | +We have slightly improved the design of the building block grid view in meshPanel. |
| 44 | +The new layout simplifies adding a new building block. We also improved its layout for smaller viewports. |
| 45 | + |
| 46 | +#### How to use |
| 47 | +You can find the improved building block grid view in the "building blocks" tab of a workspace and the |
| 48 | +"overview" tab of a tenant. |
| 49 | + |
| 50 | +### Add API Key permissions for meshPaymentMethods |
| 51 | +**Audience:** User<br> |
| 52 | + |
| 53 | +#### Description |
| 54 | +We added fine-grained API Key permissions for managing Payment Methods via the meshObject API. You can now grant |
| 55 | +API Keys explicit rights to list Payment Methods in a specific workspace or all workspaces. |
| 56 | + |
| 57 | +#### How to use |
| 58 | +When creating or editing an API Key in meshPanel, you will see new permission options for Payment Methods. Grant |
| 59 | +the required rights to allow API Keys to access or manage Payment Methods in your workspace. For more details, |
| 60 | +refer to the meshObject API documentation. |
| 61 | + |
| 62 | +### Renamed Access Tabs for Improved Clarity |
| 63 | +**Audience:** User<br> |
| 64 | + |
| 65 | +#### Description |
| 66 | +In this release, we have updated access-related tab names to enhance clarity: |
| 67 | +In the Workspace Manager, "Workspace Access" is now "Access Management" |
| 68 | +Its child tab "Current Access" is now "Role Mapping". |
| 69 | +In the project management area, "Project Access" is now also "Access Management" and its child tab |
| 70 | +"Current Access" is now "Role Mapping". |
| 71 | +These changes aim to make permissions and role management more intuitive for users. |
| 72 | + |
| 73 | +### Better Error Message For Block Runs With Missing Outputs |
| 74 | +**Audience:** User<br> |
| 75 | + |
| 76 | +#### Description |
| 77 | +The wording of the error message which is shown if a block run was marked as |
| 78 | +failed because outputs were missing or their types did not match the one |
| 79 | +specified in the definition was improved. |
| 80 | + |
| 81 | +### Empty Building Block Selection on Azure Landing Zone |
| 82 | +**Audience:** User<br> |
| 83 | + |
| 84 | +#### Description |
| 85 | +Previously, when you create landing zone of platform type "Azure", you will face an empty building block definition selection. This has been fixed. |
| 86 | + |
| 87 | +### Keyboard Accessible Card Toggles |
| 88 | +**Audience:** User<br> |
| 89 | + |
| 90 | +#### Description |
| 91 | +Expandable cards on the building blocks detail page are now accessible via keyboard. |
| 92 | +The downward-facing caret icons are focusable and operable buttons. |
| 93 | + |
| 94 | +### Fix Step Title of Building Block Run |
| 95 | +**Audience:** User<br> |
| 96 | + |
| 97 | +#### Description |
| 98 | +Fixed an issue where the first step in every building block run was always labeled |
| 99 | +"Trigger GitHub Workflow." Step titles now reflect the correct action. |
| 100 | + |
| 101 | +### README now correctly persisted |
| 102 | +**Audience:** User, Operator<br> |
| 103 | + |
| 104 | +#### Description |
| 105 | +Previously, the README value for the general information of a building block definition was not |
| 106 | +persisted in case a building block definition was created or updated via the panel. |
| 107 | +This is now fixed and works as intended. |
| 108 | + |
| 109 | +### Fixed Broken Link in Project Access View |
| 110 | +**Audience:** User<br> |
| 111 | + |
| 112 | +#### Description |
| 113 | +If you can not find a meshUser/Group within project access control then you get the information that must be assigned first to the workspace. |
| 114 | +This link was broken and now it is fixed. |
| 115 | + |
| 116 | +### Fixed Building Block Default Input Number |
| 117 | +**Audience:** User<br> |
| 118 | + |
| 119 | +#### Description |
| 120 | +We have fixed the problem with building block inputs from type number. The problem was that in case of a default value, the input was not being set correctly. |
| 121 | + |
| 122 | +### Fixed Saving Landing Zone |
| 123 | +**Audience:** User<br> |
| 124 | + |
| 125 | +#### Description |
| 126 | +We fixed an issue that prevented users from saving landing zones. The problem was when |
| 127 | +the landing zone was referenced by a deleted user the response could not be determined. |
| 128 | + |
| 129 | +### Unmanaged Tenants tab title |
| 130 | +**Audience:** User<br> |
| 131 | + |
| 132 | +#### Description |
| 133 | +The title of the Unmanaged Tenants tab in the browser was not correctly set to "Unmanaged Tenants" when the user is on the Unmanaged Tenants page. |
| 134 | +This is now fixed. |
| 135 | + |
| 136 | +### Fixed Blank Page on General Tab Switch |
| 137 | +**Audience:** Partner<br> |
| 138 | + |
| 139 | +#### Description |
| 140 | +Resolved an issue where switching back to the "General" tab in the |
| 141 | +Communication Center after visiting another tab (e.g. "Receiving Workspaces" or |
| 142 | +"Deletion") resulted in a blank screen. Users can now navigate between |
| 143 | +tabs without losing the loaded content. |
| 144 | + |
| 145 | +### Better Building Block Environment Variable Description |
| 146 | +**Audience:** Customer, Partner<br> |
| 147 | + |
| 148 | +#### Description |
| 149 | +The description texts for building block definition input variables have been improved. |
| 150 | +Now it is clearer how those variables are handed over to the building blocks. |
| 151 | + |
0 commit comments