Skip to main content

Release vNext

· 8 min read
meshcloud

Release period: 2026-07-16 to 2026-07-22

This release includes the following issues:

  • meshBuildingBlock v2-preview API refinements ahead of GA
  • meshEventLog v1-preview API refinements ahead of GA
  • meshTenant v4-preview API refinements ahead of GA
  • Chargeback Statement Project Links Stay Within Your Workspace
  • Building Blocks Column in the Tenant Overview
  • Faster Loading of Building Block Lists on Tenants and Workspaces
  • Fixed Tenant Filtering From Project Actions and Tenant Moves
  • Building Block Deletion No Longer Fails With Missing Input Variables
  • Fix Cleanup of Orphaned Building Blocks Getting Stuck on Dependencies
  • Clearer Feedback When You Trigger a Building Block Run
  • New "meshStack Tenant UUID" Input Source for Tenant Building Blocks
  • Cleaner Run Trigger Display on the Building Block Run Screen
  • Improved Badge Styling Throughout meshStack
  • meshObject API Author Details Now Include Username, Email and External ID
  • Fix Wrong Response When Creating Project User Binding with Duplicate Identifier
  • Dry Runs Now Show Whether Changes Were Detected
  • Building Block Run List Updates Smoothly While Polling

Ticket Details​

meshBuildingBlock v2-preview API refinements ahead of GA​

Audience: User

Description​

The meshBuildingBlock v2-preview meshObject API gained refinements in preparation for its upcoming GA:

  • Parent building blocks are now referenced with a structured spec.parentBuildingBlocks[].buildingBlockRef (a meshObject ref with kind and uuid). The flat buildingBlockUuid / definitionUuid fields are deprecated but still accepted and returned.
  • The unfiltered building block list now depends on the API key's permissions: the "list managed building blocks" permission returns the building blocks your workspace manages; the workspace list permission returns your workspace's own building blocks; holding both returns them together. Previously an unfiltered list never included managed building blocks unless a managedByWorkspaceIdentifier / managedByDefinitionUuid filter was set.

These deprecated fields will be removed when the API graduates from preview to GA.

meshEventLog v1-preview API refinements ahead of GA​

Audience: User

Description​

The meshEventLog v1-preview meshObject API now also exposes an event's creation information under status.created (its timestamp and author), consistent with the other meshObject APIs. The previous metadata.createdAt and spec.author fields are deprecated but still returned. The spec.workspaceRef reference is now fully described in the API reference documentation. Historical events whose author cannot be resolved are now reported with author type System, consistent with the other meshObject APIs (previously a meshEventLog-specific Unknown). The deprecated fields will be removed when the API graduates from preview to GA.

meshTenant v4-preview API refinements ahead of GA​

Audience: User

Description​

The meshTenant v4-preview meshObject API gained refinements in preparation for its upcoming GA. The tenant name is now available under status.tenantName; the equivalent status.tenantIdentifier is deprecated (still returned) as it is a display name that changes when a tenant is moved. The API reference documentation now fully describes the platformRef / landingZoneRef references and the tenant quotas. These are additive, backward-compatible preview changes. The deprecated fields will be removed when the API graduates from preview to GA.

Audience: User

Description​

In the Workspace Chargeback Statements list, the Project column now links to the project inside your workspace instead of the administration area. You stay in your workspace context and no longer need administrative permissions to follow the link.

Building Blocks Column in the Tenant Overview​

Audience: User

Description​

The tenant overview in the admin and service management areas now shows the building blocks assigned to each tenant. Every building block appears as a badge with its symbol, name and a colored status dot, so you can spot failed or in-progress building blocks across all tenants at a glance, without opening each tenant individually.

Faster Loading of Building Block Lists on Tenants and Workspaces​

Audience: User

Description​

Building Block lists on your Tenant and Workspace pages now load noticeably faster, even when a Tenant has many Building Blocks. The list loads as you scroll and stays responsive while Building Blocks are still being provisioned.

Fixed Tenant Filtering From Project Actions and Tenant Moves​

Audience: User

Description​

We fixed the Tenant list filtering when you open it from other areas of the admin section. Opening "Project Tenants" from a project's actions, or "Go to tenant list" after moving Tenants, now correctly narrows the list to the relevant Workspace and Project again instead of showing all Tenants.

Building Block Deletion No Longer Fails With Missing Input Variables​

Audience: User

Description​

We fixed a bug where deleting a Building Block could intermittently fail on missing required variables. A just-created deletion run could be picked up by a runner before its input values had become visible to the run hand-out, so the deletion started without its variables and failed. meshStack now hands out a run only once its inputs are consistently readable, so a deletion always runs with the values it needs.

Fix Cleanup of Orphaned Building Blocks Getting Stuck on Dependencies​

Audience: User

Description​

We fixed an issue where the background cleanup of building blocks orphaned on deleted tenants did not work. When one building block in a dependent family had a purge that was requested earlier but never completed, the cleanup skipped it and then failed to purge the block depending on it, failing the intended cleanup.

Clearer Feedback When You Trigger a Building Block Run​

Audience: User

Description​

When you trigger a run from the building block run screen, the feedback is now clear and consistent. For a dry run, the Trigger Run button disables and shows a loading spinner immediately, just like a regular run, and stays disabled until the run has finished, so you can't accidentally start another run while one is still in progress.

The "a run has been initiated" info message now stays visible until the new run actually appears in the list, instead of briefly flashing and vanishing before you could read it.

New "meshStack Tenant UUID" Input Source for Tenant Building Blocks​

Audience: User

Description​

You can now source a Building Block input from the meshStack-internal UUID of the Tenant a Building Block is added to. Pick the new "meshStack Tenant UUID" input source when defining an input on a tenant-level Building Block Definition, and meshStack automatically injects the Tenant's UUID at run time. Like the existing "Platform Tenant ID" source, it is only available for tenant-level Building Blocks.

Cleaner Run Trigger Display on the Building Block Run Screen​

Audience: User

Description​

We tidied up the Building Block run screen. The trigger of a run is now shown as styled plain text with an icon instead of a colored badge, so the screen looks calmer and less cluttered while still telling you at a glance what started each run.

Improved Badge Styling Throughout meshStack​

Audience: User

Description​

We refreshed the look of badges across meshStack. They now use a softer, tinted style that feels lighter and more professional, in both light and dark mode.

meshObject API Author Details Now Include Username, Email and External ID​

Audience: User

Description​

Several meshObject APIs that report the author of an action now also carry, for a user author, that user's username, email, and external identifier (euid), in addition to their identifier and display name. This applies to the trigger author of a Building Block run and the authors reported in the lifecycle information of Building Blocks and Tenants. It lets you attribute an action to the responsible person and correlate them with their identity in downstream systems. These details are included only for user authors; they are omitted for actions performed by an API key or by meshStack itself, and for users who have since been deleted.

Fix Wrong Response When Creating Project User Binding with Duplicate Identifier​

Audience: User

Description​

Creating a project user binding through the meshObject API now correctly returns a conflict error when its identifier only differs from an existing binding's identifier by casing or accented characters (for example "MyBinding" vs. "mybinding", or an accented character vs. its plain letter). Previously, such a request could unexpectedly fail with an internal server error instead of a clear conflict message.

Dry Runs Now Show Whether Changes Were Detected​

Audience: User

Description​

Dry runs of your Building Blocks now tell you whether they found changes to apply. Instead of only showing "Succeeded", a finished dry run now shows "Changes Detected" or "No Changes Detected", so you can see at a glance whether actually running the Building Block would change anything.

Runs that finished before this release always show "No Changes Detected", because we can no longer determine after the fact whether they found changes.

Building Block Run List Updates Smoothly While Polling​

Audience: User

Description​

When a Building Block has a pending, waiting, or in-progress run, we poll for updates every few seconds. Until now, each poll flashed a loading indicator over the run list and reset it back to the top, so scrolling through a longer run history kept getting interrupted. We now update the list in place: an active run's status refreshes live and a newly started run appears at the top, without any flicker and without losing your scroll position. A run that was just started elsewhere (for example by saving a change on the Building Block's settings) now also shows up on its own, instead of only after a manual page reload.