Skip to main content

Release 2026.23.0

· 8 min read
meshcloud

Release period: 2026-05-27 to 2026-06-03

This release includes the following issues:

  • meshBuildingBlock API Now Supports Updates and Run Management
  • Dry Runs for OpenTofu Building Blocks
  • Building Block Table Now Sorts by Definition and Version
  • Complete API Reference for the Building Blocks List Endpoint
  • Draft Version Indicator on Building Block Views
  • Quick Navigation to Workspace Building Blocks in Admin Area
  • API Version Selector in Docs Now Works for GET Endpoints
  • Building Block Runs Show Trigger Information
  • Drag-and-Drop Reordering for Building Block Definition Inputs and Outputs
  • Upgrade Hint for Outdated Terraform Provider in API Errors
  • Fix Spinning Loader in Building Block Run Summary
  • Restrict Building Block Output Assignment Type Options by Output Type
  • Building Block and Run Page Cleanup
  • Refresh Runner List and Guidance on Custom Runners
  • View Deleted Building Blocks in the Panel
  • User Permissions Preserved When Permission Cleanup Is Skipped
  • Improved SCIM PATCH Compatibility for Groups

Ticket Details​

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.

How to use​

Upgrading to meshStack 2026.23.0 requires upgrading the Terraform provider to v0.21.0. If you use the meshstack_building_block_v2 resource with sensitive inputs, you should also replace value_string or value_code with the new value_string_sensitive or value_code_sensitive attributes - these store the value masked in Terraform state and transmit it securely.

See the known issue post for the full upgrade guide: https://feedback.meshcloud.io/knownissues/p/meshbuildingblock-api-update-requires-terraform-provider-upgrade-to-v0210

Dry Runs for OpenTofu Building Blocks​

Audience: User

Description​

You can now trigger dry runs for your OpenTofu building blocks, with no special configuration required. A dry run previews what changes would be applied to your infrastructure without making any actual modifications, helping you validate changes safely before applying them.

How to use​

Navigate to an OpenTofu building block and open the Runs tab. Use the "Trigger Run" split button and click the dropdown arrow to select "Dry Run".

Building Block Table Now Sorts by Definition and Version​

Audience: User

Description​

We improved the default sorting order in the building block table. Building blocks are now automatically sorted first by their Building Block Definition name, then by the definition version number, and finally by the building block name. This provides a more predictable and useful overview when browsing building blocks in the Administration area.

Complete API Reference for the Building Blocks List Endpoint​

Audience: User

Description​

We improved the API reference for the Building Blocks meshObject API v2-preview. When you list Building Blocks, the response schema now documents the full Building Block structure. Previously the list response was only described as a generic array, which made it harder to discover the available fields.

Draft Version Indicator on Building Block Views​

Audience: User

Description​

When a draft version of a building block is in use, a "(Draft)" indicator is now shown next to the version name on the building block instance view and the building block card. Previously, the version appeared without any indication that it was still a draft, which could cause confusion about whether the version had already been released.

Quick Navigation to Workspace Building Blocks in Admin Area​

Audience: User

Description​

We added a Building Blocks shortcut to the workspace actions menu in the Administration area. Administrators can now jump directly from any workspace row in the workspace table to its associated building blocks with a single click.

API Version Selector in Docs Now Works for GET Endpoints​

Audience: User

Description​

We fixed a bug in the API documentation where the API version selector was not shown for GET endpoints. You can now select the desired API version for all endpoint types, including GET endpoints, and see the correct Accept header value to use in your API requests.

Building Block Runs Show Trigger Information​

Audience: User

Description​

Building Block run lists now show why a run started and who triggered it. This helps you understand whether a run was started manually or by an automated meshStack change.

Drag-and-Drop Reordering for Building Block Definition Inputs and Outputs​

Audience: User

Description​

You can now reorder inputs and outputs in building block definitions using drag-and-drop. Simply grab an item and drop it in the desired position - the new order is saved when you save the definition. This makes it easier to organize inputs and outputs in a logical sequence without having to delete and re-add them.

Upgrade Hint for Outdated Terraform Provider in API Errors​

Audience: User

Description​

Some meshObject API resources require a minimum version of the terraform-provider-meshstack. This is especially relevant for preview-versioned APIs, which receive breaking changes before reaching general availability. When your provider version is below that minimum and a request to such a resource fails, the error response now includes a resolutionHint field telling you exactly which version you need to upgrade to.

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.

Building Block and Run Page Cleanup​

Audience: User

Description​

We improved the building block and run pages with three visual updates:

  • status badges have been replaced with compact icons, showing the current state at a glance;
  • the run page now displays the building block's current status, so you have full context without navigating away;
  • the header on the run page now links to the building block definition instead of the building block itself, making it consistent with the building block page.

Refresh Runner List and Guidance on Custom Runners​

Audience: User

Description​

Building block runner selection now includes a Refresh button to reload the available runners without reloading the page. Additionally, we've added helpful guidance explaining when to use shared runners versus creating your own: use the shared runner for quick setup, or create your own runner to access internal networks, meet compliance requirements, or isolate sensitive workloads.

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.

User Permissions Preserved When Permission Cleanup Is Skipped​

Audience: User

Description​

When a platform is configured with "Skip User / Group Permission Cleanup", we now correctly preserve existing user permissions even when a tenant is in a pending deletion state (e.g. pending approval or pending resource deletion). Previously, meshStack would still remove all user permissions from the platform during these intermediate deletion states, which is not the intended behavior when this option is enabled.

How to use​

Enable "Skip User / Group Permission Cleanup" in the replicator configuration of the affected platform. meshStack will then leave all existing group and permission assignments on the platform intact throughout the entire tenant lifecycle - including deletion states - so that the platform operator can clean them up manually at a later point.

Improved SCIM PATCH Compatibility for Groups​

Audience: User

Description​

We improved compatibility for two additional SCIM PATCH operation formats for groups. First, you can now remove a specific group member using a filter expression in the path, e.g. members[value eq "meshIdentifier"]. This lets SCIM clients target individual members without sending a full value array. Second, you can now update group attributes (such as displayName or externalId) using a replace operation without an explicit "path" field, by embedding the attribute name directly inside the value object.