Skip to main content

Release 2026.37.0

· 11 min read
meshcloud

Release period: 2026-09-02 to 2026-09-09

This release includes the following issues:

  • JSON Building Block Inputs
  • Show a Building Block Input Only When It Is Relevant
  • Improved Search Accuracy for Special Characters in Admin Area
  • Building Block input descriptions now render in full
  • Fewer Failed Building Block Operations Under Heavy Parallel Load
  • Building Block Runs Under High Load - Fewer Remaining Failures
  • Clearer Error for a Tag Key That Is Too Long
  • Building Blocks Follow a Reassigned Tag Source
  • Highlight Content With GitHub-Style Warning and Info Boxes in Markdown
  • See the Building Block Name and Grouped Runner Variables in the Preview
  • Open Building Block Links With One Click
  • Clearer Run Controls on Building Blocks
  • New Overview Tab for Building Blocks
  • More Robust Building Block Runs During Identity Provider Outages
  • No More Input Notifications for Building Blocks That Were Never Created
  • Fast Changes to List Filters No Longer Get Lost
  • Microsoft Entra ID SSO Integration Now Available Everywhere

Ticket Details​

JSON Building Block Inputs​

Audience: User

Description​

Building Block inputs have a new type, JSON. Paste a JSON Schema when you declare the input and meshPanel renders a form from it, so the consumer fills in labelled fields instead of hand-writing a structured value into a code editor. A value the schema rejects is refused wherever it is set: in the form and on the meshObject API alike. The new input type sits behind a feature flag and is off by default, so ask meshcloud support to enable it for your meshStack.

How to use​

Pick "JSON" as the input type on your Building Block Definition and paste the schema. The input source must be "User Input" or "Platform Operator Input". meshPanel renders object, array, string (including enum and pattern), integer, number and boolean, nested to any depth and at the schema's root alike, so a schema with an array at its root gives the consumer a list to grow. Give a property a default in the schema to pre-fill it.

Show a Building Block Input Only When It Is Relevant​

Audience: User

Description​

You can now put a condition on a user or platform operator input of a building block definition, so that it is only asked for when it actually applies. Ask for an AWS region only after somebody picked AWS, or for a retention period only after they switched versioning on. Instead of splitting one definition into several, or documenting "leave this blank unless this applies", you keep a single definition whose form follows the choices the user has already made.

A hidden input never blocks ordering, and it is left out everywhere the input would otherwise appear: the order form, the marketplace, the input settings of an existing building block, and the version upgrade dialog. Definitions without conditions are unaffected.

How to use​

Edit an input of a draft definition version and choose "Add Condition". A condition is an expression over the other inputs of the same version, written in CEL and reading them with an input. prefix, for example input.cloud_provider == "aws". A user input can read the other user inputs; a platform operator input can read those and the other operator inputs, because you fill yours in once the user's answers are already there. We check the condition as you type - unsupported expressions, inputs that cannot be read, and conditions that read each other in a loop - and the configuration preview next to the editor lets you enter values and watch inputs appear and disappear.

While a condition does not hold, we send no value for that input to your runner, exactly as for an optional input, so your implementation has to fall back to the default declared in its own code. See our documentation on conditional inputs for what a condition can read and which expressions are supported.

Improved Search Accuracy for Special Characters in Admin Area​

Audience: User

Description​

We fixed an issue where searching in the admin project list or the service broker communication log could return unrelated results when your search term contained underscores or percent signs. These characters were previously treated as wildcards - for example, searching for "my_project" could also match "my-project" or "myXproject". The search now matches these characters literally, so you only see results that contain the exact text you typed.

Building Block input descriptions now render in full​

Audience: User

Description​

Input descriptions on your Building Block Definitions now render completely wherever we show them. Previously a description could get stuck showing only its first character, or keep showing an older version of itself, so you could not tell what your consumers would actually read.

This was most visible in the inputs preview on a Building Block Definition: as you typed a description, the preview froze on the first character you entered.

Fewer Failed Building Block Operations Under Heavy Parallel Load​

Audience: User

Description​

When many building block operations ran at the same time, for example a terraform apply creating dozens of building blocks, or a large workspace with many runs in progress, some of them could fail with an internal error although nothing was wrong with the request. You could see this when creating a building block or a building block definition, when deleting a building block, and as a run that failed within seconds of starting without ever reaching your automation.

While meshStack updates a run, it now holds on to far less of your workspace than it used to, so unrelated operations no longer get in each other's way. Operations on the same run still take their turn, and one of them can still time out when another holds that run for too long.

Building Block Runs Under High Load - Fewer Remaining Failures​

Audience: User

Description​

A recent release reduced sporadic failures of Building Block runs that happened when many runs were executed at the same time, and said we were working on the remaining cases. The platform now recovers on its own from most of them, so a run is far less likely to be reported as failed when its work in fact succeeded.

Clearer Error for a Tag Key That Is Too Long​

Audience: User

Description​

We now tell you straight away when a tag key is too long. Creating a tag definition through the API with a key longer than 255 characters returns a clear validation error naming the limit, instead of an internal error that left a half-created tag definition behind. The limit matches what meshPanel has always allowed, so keys you create in the panel are unaffected.

Tag keys of up to 255 characters now work everywhere, including as the source of a building block tag input.

Building Blocks Follow a Reassigned Tag Source​

Audience: User

Description​

A building block input sourced from a tag resolves its value from the workspace, project, payment method or landing zone the building block reads it from. Until now only editing a tag triggered a new run. If you reassigned the object the tag is read from, the input kept the value it was last resolved with, and the new value only reached your resources once an unrelated change happened to sweep it in.

We now trigger those runs on reassignment as well: funding a project from another payment method, the automatic rollover of an expired payment method to its substitute, changing a tenant's landing zone, and moving a tenant into another project. A reassignment that carries the same tag values stays quiet, so you only get a run when the value your building block reads actually changed.

We also stopped runs you never needed: a tag key that holds no value now counts as unset, whether the key is absent or holds an empty value. Saving an object for the first time after such a key appeared in your tag schema no longer re-runs the building blocks of the whole workspace.

How to use​

There is nothing to configure. See our Building Block documentation for every change that triggers a run of a building block with a tag input: https://docs.meshcloud.io/docs/concepts.building-block.html#tag-change-as-a-run-trigger

Highlight Content With GitHub-Style Warning and Info Boxes in Markdown​

Audience: User

Description​

You can now use GitHub-style alert boxes in any Markdown field across meshStack to make important information stand out. Wrapping a blockquote with > [!WARNING], > [!NOTE], > [!TIP], > [!IMPORTANT], or > [!CAUTION] renders it as a coloured, icon-labelled callout instead of a plain quote. This works everywhere Markdown is shown, including Building Block descriptions, Tenant dashboards, and Communication Definitions.

How to use​

Start a blockquote line with one of the five alert markers, then continue the quote with your content:

[!WARNING] This action deletes all resources and cannot be undone.

The box is titled and coloured automatically to match the alert type, so readers immediately see whether something is a hint, a tip, or a critical warning.

See the Building Block Name and Grouped Runner Variables in the Preview​

Audience: User

Description​

The Configuration Preview in a Building Block Definition's input editor now tells you two more things about what a workspace user gets. The resulting variables sent to the runner are grouped by how they reach it, so you can tell at a glance which values arrive as environment variables and which as regular variables. Above the form we now show the building block name a workspace user would end up with, rendered from your name template as you type.

Audience: User

Description​

When a Building Block Definition marks an output as a resource link, such as a console, a dashboard or a repository, the Building Block now shows an Open button for it instead of a long raw URL. The output's name is shown with the button, and the full URL is the tooltip, so you no longer have to read a URL to work out where it goes.

Clearer Run Controls on Building Blocks​

Audience: User

Description​

On a Building Block run's Logs page, the button that aborts or rejects a run is now red, so it stands out as a destructive action. We also only show it on runs that can actually be aborted. Previously you saw a greyed-out Abort button on runs where it could never apply.

Once you approve, reject or abort, we stop offering the action until the run has moved on, so a slow response cannot turn into a second request.

New Overview Tab for Building Blocks​

Audience: User

Description​

Building blocks now have a new Overview tab, so you can see at a glance whether one is healthy, what it produced, and what it is waiting on. It shows the reported summary, the latest run with its steps, the user inputs, the outputs, and the dependencies around it, including parent and child building blocks for the first time.

You can approve or reject a pending run right from the Overview, and when a run fails or an input is missing, we point you to the run that needs attention. The page refreshes itself while a run is in flight.

More Robust Building Block Runs During Identity Provider Outages​

Audience: User

Description​

Every building block run gets an ephemeral API key that we clean up once the run is done. We made that cleanup more robust: a run now records its result even while our identity provider is briefly unreachable, and any credential left over from such a moment is tidied up in the background.

No More Input Notifications for Building Blocks That Were Never Created​

Audience: User

Description​

As a platform operator you get notified when a building block requires your input. In rare cases you received such a notification even though the building block was never created, because an error interrupted the creation right after we had sent the notification. Following the link then led you to a building block that does not exist.

We now send this notification only once the building block has actually been created, so every notification you receive points at a building block you can really work on.

Fast Changes to List Filters No Longer Get Lost​

Audience: User

Description​

When you changed list filters in quick succession (for example toggling several options in a status filter dropdown), one of the changes could occasionally be lost, and the list kept showing results that did not match the filters you selected. We now preserve every filter change, so the results remain aligned with your selection.

Microsoft Entra ID SSO Integration Now Available Everywhere​

Audience: User

Description​

We removed the feature flag that previously restricted the Microsoft Entra ID single sign-on (SSO) integration to select meshStack environments. Users with "Organization Admin" role can now configure an Entra ID integration for their environment/meshStack without waiting for it to be enabled for their meshStack.