|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.16.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-04-09 to 2025-04-16 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Fix for building block definition input source selection |
| 10 | +* Allow changes for building block multiplicity |
| 11 | +* Tenants Column on Project Overview |
| 12 | +* Import Building Block Definitions From meshStack Hub |
| 13 | +* Mention Workspace Owner in Role Expiry Mail |
| 14 | +* Fix for landing zone role mappings |
| 15 | +* New meshObject API endpoint for communications |
| 16 | +* meshTenantUsageReport v2 API based on Chargeback 2.0 data |
| 17 | +* Workspace Identifier in URL |
| 18 | +* Improved admin area button visibility |
| 19 | +* Platform Usage Reports with Chargeback 2.0 |
| 20 | +* Allow movement of tenants with building blocks |
| 21 | +<!--truncate--> |
| 22 | + |
| 23 | +## Ticket Details |
| 24 | +### Fix for building block definition input source selection |
| 25 | +**Audience:** Customer<br> |
| 26 | + |
| 27 | +#### Description |
| 28 | +Depending on the chosen type the available input sources did not |
| 29 | +update accordingly. This is now fixed. |
| 30 | + |
| 31 | +### Allow changes for building block multiplicity |
| 32 | +**Audience:** Customer, Partner<br> |
| 33 | + |
| 34 | +#### Description |
| 35 | +Previously it was impossible to later change the multiplicity of a building block |
| 36 | +assignment from 'Multiple' to 'Once'. Now this setting can be changed at any time. |
| 37 | +Please keep in mind that meshStack will not enforce any actions to existing building blocks |
| 38 | +when a 'Multiple' building block gets changed to 'Once'. |
| 39 | + |
| 40 | +### Tenants Column on Project Overview |
| 41 | +**Audience:** Partner<br> |
| 42 | + |
| 43 | +#### Description |
| 44 | +We have added the tenants column back to the project overview in the admin area. |
| 45 | + |
| 46 | +### Import Building Block Definitions From meshStack Hub |
| 47 | +**Audience:** User<br> |
| 48 | + |
| 49 | +#### Description |
| 50 | +You can now directly import building block definitions from our new meshStack Hub (hub.meshcloud.io) into your own meshStack. Simply open up a building block definition of choice, click "Add to meshStack", enter your meshStack URL and you will be redirected to import the building block definition. |
| 51 | + |
| 52 | +### Mention Workspace Owner in Role Expiry Mail |
| 53 | +**Audience:** User<br> |
| 54 | + |
| 55 | +#### Description |
| 56 | +The workspace owner(s) are now mentioned in the mail when your workspace role is about to expire. |
| 57 | +This should make it easier to identify whom to contact in case you are a workspace member |
| 58 | +and need your role extended. |
| 59 | + |
| 60 | +### Fix for landing zone role mappings |
| 61 | +**Audience:** Customer<br> |
| 62 | + |
| 63 | +#### Description |
| 64 | +This fixes a UI regression bug that broke the configuration of most platforms' role |
| 65 | +mappings in landing zone configurations. |
| 66 | + |
| 67 | +### New meshObject API endpoint for communications |
| 68 | +**Audience:** Partner<br> |
| 69 | + |
| 70 | +#### Description |
| 71 | +The meshObject API in meshStack now provides new endpoints for meshCommunicationDefinitions and meshCommunications. Please be aware that these endpoints are still in a preview state and we will release the final endpoints in the upcoming weeks. More details on preview endpoints are described in the API documentation. |
| 72 | + |
| 73 | +### meshTenantUsageReport v2 API based on Chargeback 2.0 data |
| 74 | +**Audience:** Partner<br> |
| 75 | + |
| 76 | +#### Description |
| 77 | +The meshTenantUsageReport v2 API is now based on Chargeback 2.0 data. It still used data from |
| 78 | +the old process before. No change to the result is expected. Please remember, that the meshTenantUsageReport |
| 79 | +v2 API will be deprecated on Oct 1st 2025. Please switch your integrations to v3. |
| 80 | + |
| 81 | +### Workspace Identifier in URL |
| 82 | +**Audience:** User<br> |
| 83 | + |
| 84 | +#### Description |
| 85 | +The workspace identifier is now part of the URL. This enables deeplinks to |
| 86 | +specific workspaces. You can now share links to specific workspaces |
| 87 | +with other users, making it easier for them to access the information |
| 88 | +they need. |
| 89 | + |
| 90 | +### Improved admin area button visibility |
| 91 | +**Audience:** Partner<br> |
| 92 | + |
| 93 | +#### Description |
| 94 | +The admin area button is now shown all the time to allow administrators to jump quickly |
| 95 | +to the admin area dashboard. |
| 96 | + |
| 97 | +### Platform Usage Reports with Chargeback 2.0 |
| 98 | +**Audience:** Partner<br> |
| 99 | + |
| 100 | +#### Description |
| 101 | +The platform usage reports shown in the admin area within the platform control plane are |
| 102 | +now also based on Chargeback 2.0 data. You should not notice any difference in the reports. |
| 103 | + |
| 104 | +### Allow movement of tenants with building blocks |
| 105 | +**Audience:** Partner<br> |
| 106 | + |
| 107 | +#### Description |
| 108 | +This fixes a bug that broke building blocks on a workspace if a tenant with building blocks |
| 109 | +on it was moved into this workspace. |
| 110 | + |
0 commit comments