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

Commit 9c5441e

Browse files
author
GitHub Actions
committed
Added release notes and version entries for 2025.18.0
1 parent f00d798 commit 9c5441e

File tree

1 file changed

+95
-0
lines changed

1 file changed

+95
-0
lines changed
Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
author: meshcloud
3+
title: Release 2025.18.0
4+
---
5+
6+
Release period: 2025-04-23 to 2025-04-30
7+
8+
This release includes the following issues:
9+
* Shows Building Block Input Description in Overview
10+
* Improved Cooldown Handling for Notifications
11+
* File Type Removed as User Input from Building Blocks
12+
* Allow Title and Content Changes to Published Communications
13+
* Broken Open Source Information in Panel
14+
* Fix Multirole Mapping for GCP Landing Zones
15+
* Communications can now target Tenants and BBDs
16+
* Improved Error Handling for Github Building Block Runner
17+
* Introduction of Communication Center Light
18+
<!--truncate-->
19+
20+
## Ticket Details
21+
### Shows Building Block Input Description in Overview
22+
**Audience:** User<br>
23+
24+
#### Description
25+
This change adds the input description field when the user opens the building block details
26+
view. Showing the description helps understand the meaning of a particular input field when a
27+
user later edits it.
28+
29+
### Improved Cooldown Handling for Notifications
30+
**Audience:** User<br>
31+
32+
#### Description
33+
This fixes a bug that could, for certain message topics, result in notifications getting re-sent before
34+
their intended cooldown period was over. This resulted in an unexpectedly higher notification frequency.
35+
36+
### File Type Removed as User Input from Building Blocks
37+
**Audience:** User, Customer<br>
38+
39+
#### Description
40+
It was sometimes possible to choose file type as user input for building blocks.
41+
This is not supported and did not work. The option should not have been selectable but it was
42+
under certain circumstances.
43+
If you have already created a building block definition with such a combination please create
44+
a new version of it and fix this input type.
45+
46+
### Allow Title and Content Changes to Published Communications
47+
**Audience:** Partner<br>
48+
49+
#### Description
50+
Users can now update the title and content of published communications.
51+
Changes are applied instantly across workspace and admin views.
52+
53+
### Broken Open Source Information in Panel
54+
**Audience:** Partner, Operator<br>
55+
56+
#### Description
57+
There was an issue with Open Source Information in the panel, where SBOM was not downloadable and license information was not displayed.
58+
This has been fixed. The SBOM is now downloadable, and the license information is displayed correctly.
59+
60+
### Fix Multirole Mapping for GCP Landing Zones
61+
**Audience:** Customer, Partner<br>
62+
63+
#### Description
64+
This fixes the regression which was recently introduced and broke
65+
the configuration of multiple GCP role bindings for the GCP landing zones.
66+
67+
### Communications can now target Tenants and BBDs
68+
**Audience:** Operator, Customer<br>
69+
70+
#### Description
71+
Communication definitions are no longer limited to targeting workspaces. They can now also target specific building block definitions and tenants. This enables more granular communication scenarios, such as platform-specific announcements or messages directed at affected tenants. By decoupling communications from the workspace level, this change supports greater flexibility in the meshObject lifecycle (e.g., tenant or project migrations, deletions, or tagging-based targeting).
72+
73+
#### How to use
74+
When creating a communication definition, use the filter criteria or API to specify target building block definitions or tenants, either by UUID or by tag. The system will resolve and create one communication per resolved object. workspace ownership is still inferred indirectly via the selected object.
75+
76+
### Improved Error Handling for Github Building Block Runner
77+
**Audience:** User<br>
78+
79+
#### Description
80+
If there is a problem while communicating with Github the error handling
81+
was improved. This results in better error signaling on the affected building
82+
block runs.
83+
84+
### Introduction of Communication Center Light
85+
**Audience:** Partner, Customer, User<br>
86+
87+
#### Description
88+
The communication center 'light' is now available for users of the Developer
89+
Portal Module. Please refer to previous release notes for more details on the
90+
communication center. The light version includes a limited feature set of
91+
the communication center where communications can be targeted towards
92+
workspaces or platforms. Please also note that meshObject endpoints related
93+
to communications are disabled with the light version. Please contact sales
94+
if you would like to upgrade to the full version.
95+

0 commit comments

Comments
 (0)