Skip to main content

Release vNext

· 3 min read
meshcloud

Release period: 2026-05-27 to 2026-05-29

This release includes the following issues:

  • Fix Spinning Loader in Building Block Run Summary
  • Restrict Building Block Output Assignment Type Options by Output Type
  • View Deleted Building Blocks in the Panel
  • meshBuildingBlock API Now Supports Updates and Run Management

Ticket Details

Fix Spinning Loader in Building Block Run Summary

Audience: User

Description

We fixed a bug where the loading spinner in the building block run Summary box kept spinning even after the run had already reached a final state (e.g. failed or succeeded). The spinner now correctly disappears once the run is complete.

Restrict Building Block Output Assignment Type Options by Output Type

Audience: User

Description

When configuring building block definition outputs, the available assignment type options are now filtered based on the selected output type. For example, INTEGER and BOOLEAN outputs only support "None", while STRING outputs support all assignment types. This prevents invalid combinations and reduces configuration errors.

How to use

When editing a building block definition version, navigate to the Outputs section. After selecting an output type, the assignment type dropdown will automatically show only the options that are valid for that type. If you change the output type to one that no longer supports the currently selected assignment type, the assignment type will reset to "None" automatically.

View Deleted Building Blocks in the Panel

Audience: User

Description

You can view deleted building blocks in the overview table. They are shown by default, but you can also filter specifically for them by selecting the "Deleted" status filter.

You can also open them, view their past runs and inspect their logs.

meshBuildingBlock API Now Supports Updates and Run Management

Audience: User

Description

We extended the meshBuildingBlock API with new capabilities for managing building blocks and their runs.

You can now update building block inputs in place using a PUT request, without having to delete and recreate the building block. After updating inputs, you can retrigger a new run via a dedicated action endpoint. This enables automation workflows that modify building block configurations and apply changes incrementally.

We also added a new endpoint to list building block runs filtered by building block, and an extra endpoint to download logs on individual runs that returns structured step including status and messages.

When runTransparency is enabled on a building block definition, workspace-scoped API keys can retrigger runs and access full run logs including system messages. The building block response also includes input definition metadata such as assignment type and value type.