Skip to main content

Release vNext

· 5 min read
meshcloud

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

This release includes the following issues:

  • Fixed Tenant Filtering From Project Actions and Tenant Moves
  • Building Block Deletion No Longer Fails With Missing Input Variables
  • 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
  • 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​

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.

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.

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.