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

Commit 02d00cb

Browse files
author
GitHub Actions
committed
Added release notes and version entries for 2025.43.0
1 parent 5a462a8 commit 02d00cb

File tree

1 file changed

+80
-0
lines changed

1 file changed

+80
-0
lines changed

blog/2025-10-08-Release-0.md

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
---
2+
author: meshcloud
3+
title: Release 2025.43.0
4+
---
5+
6+
Release period: 2025-10-01 to 2025-10-08
7+
8+
This release includes the following issues:
9+
* Building Block Definitions Filter Results Improvement
10+
* Fix Rare Race Condition in Tenant Replication
11+
* Improved Workspace Role Expiration Alert Modal
12+
* Fix Authentication in OpenStack With Custom Configuration
13+
* View Runner assigned to Building Block Definition
14+
* Prevent Stuck Building Block Upgrades
15+
* Improved meshPlatform API Validation for Publication Status
16+
<!--truncate-->
17+
18+
## Ticket Details
19+
### Building Block Definitions Filter Results Improvement
20+
**Audience:** User<br>
21+
22+
#### Description
23+
The building block definitions overview page now shows proper message in the table when applied
24+
filters don't match any definitions, instead of showing the empty state. This provides clearer
25+
feedback that definitions exist but are filtered out.
26+
27+
### Fix Rare Race Condition in Tenant Replication
28+
**Audience:** User<br>
29+
30+
#### Description
31+
We fixed an issue where a race condition could occur during tenant replication. In very rare cases, when a new tenant
32+
replication was triggered while a retry of a previous replication was still running, the newer replication failed
33+
but was never retried. This could lead to tenants remaining in the failed state until the nightly replication.
34+
Tenant replications will now be handled correctly even when multiple replication attempts overlap, ensuring that
35+
the most recent replication request is always processed.
36+
37+
### Improved Workspace Role Expiration Alert Modal
38+
**Audience:** User<br>
39+
40+
#### Description
41+
The workspace role expiration alert modal has been enhanced with a better layout and clearer navigation.
42+
The modal now displays workspace expiration information in a more structured format with direct "Go to
43+
Workspace" buttons for each workspace, making it easier to extend or modify access permissions.
44+
45+
### Fix Authentication in OpenStack With Custom Configuration
46+
**Audience:** User<br>
47+
48+
#### Description
49+
We fixed an issue where OpenStack authentication would fail when configuring a custom project or domain.
50+
The platform now correctly uses the configured domain and project values for authentication.
51+
52+
### View Runner assigned to Building Block Definition
53+
**Audience:** User<br>
54+
55+
#### Description
56+
Platform engineers can now see which runner is associated with a building block definition version in the "Implementation"
57+
tab of the building block definition. This information enables you to access the workload identity federation information
58+
for that runner.
59+
60+
#### How to use
61+
Navigate to a building block definition implementation in the platform builder or admin area to see its associated runner.
62+
Changing the runner assignment is not yet supported but will be available in a future update.
63+
64+
### Prevent Stuck Building Block Upgrades
65+
**Audience:** User<br>
66+
67+
#### Description
68+
We fixed an issue where building block upgrades could get stuck when you triggered an upgrade while a
69+
building block run was still in progress. Now we prevent you from upgrading a building block if its
70+
current run hasn't finished yet, ensuring your upgrades complete successfully.
71+
72+
### Improved meshPlatform API Validation for Publication Status
73+
**Audience:** User<br>
74+
75+
#### Description
76+
We improved validation for the meshPlatform API to ensure that when you create a meshPlatform, it must be in a
77+
publication status of either PUBLISHED or UNPUBLISHED. If you attempt to create a meshPlatform with an invalid
78+
publication status, the API now returns a clear and meaningful error message explaining the requirement. This helps
79+
prevent configuration errors and provides better guidance when working with the meshPlatform API programmatically.
80+

0 commit comments

Comments
 (0)