Skip to main content

Release 2026.27.0

· 9 min read
meshcloud

Release period: 2026-07-06 to 2026-07-08

This release includes the following issues:

  • Correct Run Button Caption When a Default Value Is Applied
  • Workspace and Project Access Lists Now Keep a Stable Order
  • Composition Building Blocks Can Keep Their Child Blocks Up to Date
  • Apply Runs No Longer Get Stuck as Dry Runs After Waiting for Input
  • More Reliable Deletion of Building Blocks and Their Definitions
  • Choose STACKIT as a Supported Platform for Building Blocks
  • Preserve the Order of Building Block Definition Inputs and Outputs
  • Preserve the Order of Selectable Values in Selection Inputs
  • Deactivated Platform Types Are Hidden for New Platforms
  • Faster Building Block Definition Search
  • Streamlined Tenant List With Consolidated Columns and New Actions Column
  • Provide Files as Customer Input for Building Blocks
  • Fix Reactivating a Deprecated Platform for Platform Operators
  • Clearer Azure Subscription Creation Error Messages
  • Billing Data Is Now Purged When You Delete a Platform
  • Fix Building Block Run Status Polling Building Up Over Time

Ticket Details​

Correct Run Button Caption When a Default Value Is Applied​

Audience: User

Description​

When you re-run a Building Block and one of its inputs takes a default value from the Building Block Definition, the run button now correctly reads "Save & Run" instead of "Run without changes".

Workspace and Project Access Lists Now Keep a Stable Order​

Audience: User

Description​

The list of users and groups on a Workspace or Project could show up in a different order every time you reloaded it or changed anything, which made it hard to find an entry once the list grew. We now sort these access lists deterministically, so the order stays the same across reloads and operations. The same fix applies to the pending access request lists.

Composition Building Blocks Can Keep Their Child Blocks Up to Date​

Audience: User

Description​

A composition building block, for example a starter kit that sets up several building blocks for you, can now keep the building blocks it created up to date when you manage it as the owner of its definition. When it runs again, it moves them to newer versions and applies the platform-operator settings your platform team manages, so your starter kits stay current without anyone updating each block by hand. Application teams consuming a starter kit still cannot upgrade those blocks or set operator inputs themselves: only the composition, acting for the platform team that owns the definitions, can.

Apply Runs No Longer Get Stuck as Dry Runs After Waiting for Input​

Audience: User

Description​

When a dry run was waiting for a missing input and you then provided that input on the Building Block, the newly scheduled apply run reused the waiting run but was still treated as a dry run. As a result, the Building Block was not updated with the run result. The reused run now correctly switches to an apply run, so setting the missing input triggers a real deployment as expected. A run that is still waiting to execute now also shows the Building Block's current definition version instead of the version from when the run was originally created.

More Reliable Deletion of Building Blocks and Their Definitions​

Audience: User

Description​

We fixed a rare edge case where deleting a Building Block and its Building Block Definition in quick succession could fail with an internal error. Deletion now completes reliably even when a late provisioning result for the block arrives at the same time.

Choose STACKIT as a Supported Platform for Building Blocks​

Audience: User

Description​

You can now select STACKIT as a supported platform when creating a tenant-level building block definition. This lets you build and offer building blocks tailored to your STACKIT tenants directly from the marketplace.

Preserve the Order of Building Block Definition Inputs and Outputs​

Audience: User

Description​

Building Block Definitions now keep the order of their inputs and outputs exactly as you arrange them, both when you reorder them in the Panel and when you define them through the meshObject API, instead of applying an implicit order. This gives you full control over how inputs and outputs appear to your users.

Preserve the Order of Selectable Values in Selection Inputs​

Audience: User

Description​

Selection-type inputs of a Building Block Definition now keep the order of their selectable values exactly as you define them through the meshObject API or via the Panel. This lets you control how the dropdown options are presented to your users.

Deactivated Platform Types Are Hidden for New Platforms​

Audience: User

Description​

Deactivated platform types no longer appear when you create a new Platform, so new Platforms are only ever built on types you still support.

Audience: User

Description​

We sped up searching and listing building block definitions. If your organization manages many building block definitions, the marketplace and administration lists now load noticeably faster, especially as your catalog grows.

Streamlined Tenant List With Consolidated Columns and New Actions Column​

Audience: User

Description​

We streamlined the tenant list in the admin and service management areas. The new "Tenant" column combines the former "Tenant ID", "Platform", "Location" and "Landing Zone" columns: each entry shows the tenant ID as a link to the tenant details, the platform with its location, and the landing zone name at a glance. The new "Hierarchy" column merges the former "Workspace" and "Project" columns and shows the workspace and project of each tenant as a breadcrumb, matching the look and feel of the Building Block list.

In addition, a new "Actions" column replaces the previous "Quota Request" column. It surfaces everything that needs your attention or is currently in flight on a tenant: pending quota requests, pending deletion approvals, replications in progress and deletions in progress. You can filter the list by these states, including "Any" to see all tenants that need attention and "None" to hide them.

Finally, a new leading "Status" column replaces the "Replication" and "Last replication" columns. It shows the final replication result as a check or cross icon and can be filtered by it, while in-flight replications appear in the "Actions" column. Hovering over the status icon reveals the replication result, who triggered the latest replication, and when it ran. The "Totals" cards that previously sat above the list have been removed in favor of filtering the list by these states directly.

How to use​

Use the search fields above the "Tenant" and "Hierarchy" columns to search across all their combined values: tenant ID, platform, location and landing zone name in the "Tenant" column, or workspace and project identifiers in the "Hierarchy" column. You can enter multiple terms separated by spaces and results will match all of them, e.g. "azure dev".

In the admin area, the "Actions" column offers an "Approve Quota Request" button that takes you to the tenant details and an "Approve Tenant Deletion" button that takes you to the Deleted Tenants view, prefiltered to the tenant at hand. In the service management area the same states appear as status texts.

Note: on upgrade, the tenant inventory search index is rebuilt once. On large installations the list may briefly show incomplete results until the index has caught up.

Provide Files as Customer Input for Building Blocks​

Audience: User

Description​

You can now upload a file when you fill in a customer input for a Building Block. Previously file inputs were only available for Platform Operators or as static values. When you configure a Building Block, inputs of type File now show an upload widget where you can select a file, preview its contents, and reset your selection.

Fix Reactivating a Deprecated Platform for Platform Operators​

Audience: User

Description​

We fixed a bug where platform operators could not reactivate their own platform after deprecating it in the Platform Builder danger zone. The "Reactivate platform" button failed with a generic server error, and only meshStack administrators were able to bring the platform back. Now platform operators can reactivate their own platform themselves, just like they can deprecate it.

Clearer Azure Subscription Creation Error Messages​

Audience: User

Description​

When creating an Azure Subscription fails, we now surface the actual reason Azure reported instead of a generic communication error. For example, if an Azure policy such as "blockSubscriptionsLeavingTenant" prevents the creation, you now see that specific reason directly in the replication status. This kind of policy error is also now reported as a clear failure instead of being kept pending during the retry cooldown.

Billing Data Is Now Purged When You Delete a Platform​

Audience: User

Description​

When you delete a Platform, we now automatically remove all of its metering and usage data from our billing service. This includes the per-Platform metering database, its tenant usage reports and the related background subscriptions. This keeps your billing storage clean and frees up resources that are no longer needed once a Platform is gone.

The aggregated billing history shown in meshStack is intentionally kept, so your past reports and chargeback records remain available even after a Platform has been deleted.

How to use​

When you open a deleted Platform in the Panel, hint texts now make this behavior clear: the Danger Zone, the metering status and the Platform's usage reports all indicate that billing data collection stopped immediately upon deletion, while previously collected usage reports remain available.

Fix Building Block Run Status Polling Building Up Over Time​

Audience: User

Description​

We fixed an issue on the Building Block and Building Block Run pages where the automatic polling for run status could pile up. While a Building Block had an active run, navigating between its tabs (for example Runs and Settings, or a run's Logs and Inputs & Outputs) added extra polling loops that never stopped, causing a growing number of background requests and unnecessary load on your browser and the meshStack backend.