Skip to main content

Release vNext

· 5 min read
meshcloud

Release period: 2026-10-14 to 2026-10-16

This release includes the following issues:

  • See Orphaned Workspaces in the Admin Area
  • Links That Open Building Blocks, Tenants and More in the Right View
  • Stricter Checks for Building Block Upgrades and Inputs
  • Building Blocks Drop Outputs Removed in a Newer Definition Version
  • Deleting a Building Block That Never Ran No Longer Blocks the Workspace
  • Building Block Definitions Refuse an Invalid Input Regex
  • Building Blocks No Longer Fail After Another Building Block Finished Deleting
  • Approve and Abort Building Block Runs via the meshObject API

Ticket Details​

See Orphaned Workspaces in the Admin Area​

Audience: User

Description​

You can now spot workspaces that nobody looks after anymore, before their costs grow unnoticed. A workspace is orphaned when it is not deleted but has no active Workspace Owner or Workspace Manager left, for example after the last one was removed via SCIM, was disabled, or their role binding expired. Owners and managers who get their role through a group still count, as long as the group has at least one active member. An invited owner who has not logged in yet also counts, so a newly created workspace is not reported as orphaned.

How to use​

"Actions Needed" on the admin area dashboard now shows how many workspaces are orphaned. Click the entry to open the workspace list filtered to these workspaces. In the workspace list you can also pick "Orphaned" in the status filter, and every orphaned workspace carries an "Orphaned" status badge.

Audience: User

Description​

Copilot answers now link a building block definition or a platform to the best view the reader has access to: the admin area, the workspace that operates it, or the marketplace of their own workspace.

The meshObject API now returns a meshPanel link for building blocks, building block runs, building block definitions, tenants, projects, workspaces, platforms and integrations, which opens the object in the best view the user has access to, like the links in Copilot answers.

Stricter Checks for Building Block Upgrades and Inputs​

Audience: User

Description​

We tightened who may set which building block inputs when you order or upgrade a building block through meshPanel, so these actions now follow the same rules as the meshObject API.

Only platform administrators and the platform team that owns the building block definition may upgrade a building block. Application teams never saw the upgrade option in meshPanel, but the underlying request was not refused for them. It is now.

When you order a building block in meshPanel, meshStack now ignores values for inputs that it fills in itself, such as static inputs. Platform operator inputs are only accepted from platform administrators and the platform team that owns the definition.

Building Blocks Drop Outputs Removed in a Newer Definition Version​

Audience: User

Description​

Before, a building block kept showing an output after you removed it from its building block definition and upgraded the building block to the new version. The removed output and its old value stayed in the Panel and in the API, even after the building block ran again. We have fixed this: after a successful run, a building block only shows the outputs that its building block definition version declares. Building blocks that still show a removed output lose it with their next successful run. Dry runs do not remove outputs.

Deleting a Building Block That Never Ran No Longer Blocks the Workspace​

Audience: User

Description​

We fixed a bug that occurred when you deleted a building block whose run had not started yet, for example because it was still waiting for an input or for a runner. The deletion was not processed, and as long as that building block stayed in deletion, we also ignored every other building block change in the same workspace: new building blocks, input changes and further deletions did not run, and the affected building blocks were set to failed after a few hours. Such a building block is now removed right away, and the other building blocks in the workspace are processed as usual.

Building Block Definitions Refuse an Invalid Input Regex​

Audience: User

Description​

A building block definition version is now refused if the validation regex of one of its inputs is not a valid regular expression. The error names the input. Until now such a version could be saved, and the regex then let every value through in the meshObject API.

How to use​

Only the version you save is checked; versions you saved before stay as they are. A Terraform apply that sends an existing version with such a regex again now fails, so fix the regex in your configuration before you apply it.

Building Blocks No Longer Fail After Another Building Block Finished Deleting​

Audience: User

Description​

When you created or changed a building block while another building block in the same workspace finished its deletion, we could lose your change. Your building block then stayed pending and failed hours later without a reason. We now apply your change in this situation, and the deleted building block stays deleted.

Approve and Abort Building Block Runs via the meshObject API​

Audience: User

Description​

You can now approve or reject a building block run that waits for approval, and abort a running one, with an API key or the meshStack CLI. An approval only applies the plan you reviewed. Approving and rejecting stay with the platform team that owns the building block definition.