Skip to main content

Release 2026.25.0

· 8 min read
meshcloud

Release period: 2026-06-11 to 2026-06-24

This release includes the following issues:

  • Restricted and Default Tags for Landing Zones and Building Block Definitions
  • meshTenantUsageReport.v1 API Endpoint Retired
  • Fixed Workspace Name Filter In Communication Center
  • Markdown Now Renders in Building Block Input Descriptions
  • Deletion Dialogs Now Inform About Pending Tenant Confirmations
  • Clear Error When Filtering Integrations by an Invalid Type
  • Clear Error When Filtering Building Blocks by an Invalid Status
  • Fix Incorrect Memory Metering for Kubernetes Pods With Large Memory
  • Fixed Kubernetes Usage Collection for API Server URLs With a Trailing Slash
  • Manage Building Blocks via API Keys Using Definitions You Own
  • Fix Case-Only Renames of Building Block Definition Inputs Failing
  • Automatic Login for Users with an Active Session
  • Building Block Run History Now Available After Building Block Deletion
  • Support for AWS European Sovereign Cloud Platform
  • Expired Project Access Uses the New Access Control View
  • Enriched Deletion Author in meshBuildingBlock v2 API

Ticket Details​

Restricted and Default Tags for Landing Zones and Building Block Definitions​

Audience: User

Description​

You can now mark tags on Landing Zones and Building Block Definitions as restricted, just like you already can for Workspaces and Projects. Restricted tags can only be set or changed by administrators in the Admin Area, while users who create or edit these objects in the Platform Builder only see and manage the unrestricted tags.

Restricted tags can also define a default value. When a user creates a new Landing Zone or Building Block Definition, these defaults are applied automatically upon creation, so your governance tags are populated from the start.

How to use​

Open the tag administration area and select Landing Zone or Building Block Definition. When you create or edit a tag, enable the Restricted option to limit editing to administrators, and optionally set a default value that is pre-filled when the object is created.

meshTenantUsageReport.v1 API Endpoint Retired​

Audience: User

Description​

We have retired the meshTenantUsageReport v1 API endpoint. This endpoint was planned for retirement since October 2025. Calling it now returns HTTP 406 Not Acceptable.

Please upgrade to meshTenantUsageReport.v3, which includes line items at seller-product-group aggregation level and supports report versioning and cancellation tracking.

How to use​

Update your API client to use the v3 media type: application/vnd.meshcloud.api.meshtenantusagereport.v3.hal+json

Fixed Workspace Name Filter In Communication Center​

Audience: User

Description​

When you filtered workspaces by name while creating a new Communication, the results could wrongly include soft-deleted workspaces and partner workspaces. This is now fixed.

Markdown Now Renders in Building Block Input Descriptions​

Audience: User

Description​

Building block input descriptions now render markdown formatting correctly on the edit inputs screen. Previously, markdown syntax was displayed as raw text instead of formatted output.

Deletion Dialogs Now Inform About Pending Tenant Confirmations​

Audience: User

Description​

When deleting a workspace or project in the admin area, you now see a note that some tenants may require manual admin confirmation before they are fully deleted. A direct link to the deleted tenants list helps you quickly identify and confirm those tenants so the deletion can complete.

Clear Error When Filtering Integrations by an Invalid Type​

Audience: User

Description​

When you list Integrations through the meshObject API with a type filter value that does not exist, the API now responds with a clear 400 Bad Request that lists the valid type values, instead of failing with a generic internal server error. Valid type filters keep working exactly as before.

Clear Error When Filtering Building Blocks by an Invalid Status​

Audience: User

Description​

When you list Building Blocks through the meshObject API with a status filter value that does not exist, the API now responds with a clear 400 Bad Request that lists the valid status values, instead of failing with a generic internal server error. Valid status filters keep working exactly as before.

Fix Incorrect Memory Metering for Kubernetes Pods With Large Memory​

Audience: User

Description​

We fixed a bug that could cause incorrect memory metering for Kubernetes tenants when pod memory limits were specified as plain byte values of 2 GiB or more (e.g., 4294967296 instead of 4Gi). In affected cases, the value was silently corrupted, leading to wrong chargeback statements. Most users are unaffected, as memory limits are typically specified with a unit suffix like Gi or Mi.

Fixed Kubernetes Usage Collection for API Server URLs With a Trailing Slash​

Audience: User

Description​

We fixed a bug that broke usage collection for Kubernetes platforms whose API server URL was configured with a trailing slash (for example "https://api.k8s.example.com:6443/"). For these Platforms, metering data such as Pod and Persistent Volume Claim usage could not be collected, which could lead to missing usage and incomplete billing. Usage collection now works regardless of whether the configured API server URL ends with a slash.

Manage Building Blocks via API Keys Using Definitions You Own​

Audience: User

Description​

You can now grant an API key permission to update building blocks that use building block definitions your workspace owns, including building blocks in other workspaces. This lets platform teams set operator inputs on building blocks programmatically, for example to fill in platform operator fields, without handing out broad administrative access. The permission only allows updating existing building blocks of your own definitions; it does not allow creating building blocks in other workspaces.

Fix Case-Only Renames of Building Block Definition Inputs Failing​

Audience: User

Description​

We fixed a bug where renaming a building block definition input by changing only its casing (e.g. role_arn -> ROLE_ARN) caused a 500 Internal Server Error. The API now handles case-only renames correctly, so you can update your input keys without running into this error.

Automatic Login for Users with an Active Session​

Audience: User

Description​

Previously, opening meshPanel in a new browser tab or window always showed the welcome page, and you had to click "Login" again even though you were already signed in. meshPanel now detects your active session when you open it and signs you in automatically, taking you straight to your workspace, administration area or landing page.

How to use​

No action is required. When you open meshPanel while your session is still active, we sign you in automatically. If you logged out or your session expired, you will see the welcome page as before.

Building Block Run History Now Available After Building Block Deletion​

Audience: User

Description​

We fixed an issue where the building block run API returned a 404 error when you queried runs for a building block that had since been deleted. The runs were always stored in the database - only the building block itself was soft-deleted - but the API incorrectly treated the deleted building block as if it never existed.

You can now retrieve the full run history for a building block even after it has been deleted. This is especially useful when using tools like 'tofu test', which creates a building block, runs it, and then tears it down on failure - previously leaving the run history inaccessible via the API.

Support for AWS European Sovereign Cloud Platform​

Audience: User

Description​

You can now configure AWS platforms in meshStack using the AWS European Sovereign Cloud (ESC), a new, fully isolated AWS partition designed for European data-sovereignty requirements. ESC uses the region eusc-de-east-1 and generates ARNs with the arn:aws-eusc: prefix automatically.

How to use​

To set up an ESC platform, configure your AWS platform connection with the region eusc-de-east-1. meshStack will detect the ESC partition and use the correct ARN format and API endpoints automatically.

Expired Project Access Uses the New Access Control View​

Audience: User

Description​

The Expired Project Access view now uses our redesigned access control layout, so it looks and behaves consistently with the rest of project access management. You can still edit and remove expired role bindings directly from this view.

Enriched Deletion Author in meshBuildingBlock v2 API​

Audience: User

Description​

We enriched the markedForDeletionBy field in the meshBuildingBlock v2 API. Instead of a plain identifier string, it now returns a structured author object with an identifier, a human-readable display name, and an author type. This gives you full visibility into whether a deletion was triggered by a user, an API key, an API user, or the system.

Breaking change: If you consume the markedForDeletionBy field of the meshBuildingBlock v2-preview API, you must adapt your client to the new structured format.