Skip to main content

Release 2026.47.0

· 19 min read
meshcloud

Release period: 2026-11-11 to 2026-11-18

This release includes the following issues:

  • Approving Building Block Runs Needs a Full Access CLI Login
  • Hide a Platform from the Marketplace
  • A Dedicated Permission to Approve Building Block Runs
  • Workspace Members Can Read Usage Reports of Their Projects via API and CLI
  • Workspace Members Can Read the Tenants of Their Projects via API and CLI
  • Show Building Block Inputs Only on the Landing Zones That Need Them
  • Try Out a Landing Zone in the Building Block Configuration Preview
  • Create Projects and Tenants While Adding a Building Block
  • Building Blocks Show the Name of Their Payment Method Again
  • Organization Admins Can Manage Project Role Bindings with the meshStack CLI
  • Direct Links to Creation Dialogs Fixed
  • Create a Tenant from an Empty Project
  • Newest Projects First on the Workspace Overview
  • meshCommunication Target Uses the Standard Reference Shape
  • Four-Eyes Approval Now Also Applies to Role Bindings Made Through the API
  • Turn on the Platform Builder from the Marketplace
  • See Recent Usage Reports on the Tenant Details Page in the Admin Area
  • Clear Guidance When Marketplace Services Block Project Deletion
  • Unused Built-in Platform Types Are Deactivated With Lightweight Platforms
  • Find the Default Building Block Runner in the API
  • Platform Settings Reject an Empty Tag Prefix
  • Switch Off Tag Replication for a Platform
  • See When and by Whom a Communication Was Created via the API
  • Kind Is Now Required in the Communication Definition Reference
  • Undelete a Building Block Whose Deletion Failed
  • See Which Projects Miss a Payment Method in the Workspace Overview
  • Security Fix: Authorization Issue (SA-2026-02)
  • Simplified Tenant Creation
  • New Tenants First on the Project Tenants Page
  • General Availability for the meshBuildingBlock v2 API
  • General Availability for the meshBuildingBlockDefinition v1 API
  • Admins Can Delete a Tenant from the Admin Area
  • Tag Selections Show the Same Name in the List and the Field
  • Send Platform Notification Mails to a Team Mailbox
  • Move Tenant Wizard Only Warns About Policy Violations a Move Would Cause
  • Screen Readers Read the Wizard Button as It Is Shown
  • Platform Types List Shows Active Platform Types by Default
  • Improved Workspace Isolation for Building Blocks in the meshObject API

Ticket Details​

Approving Building Block Runs Needs a Full Access CLI Login​

Audience: User

Description​

A meshStack CLI login now needs full access to approve or reject a building block run that waits for approval. A "safe access" login (called "no delete" before) or a read-only login can no longer do this, so you can give such a login to an AI agent or a script that changes building blocks, while you keep the decision to apply those changes.

Hide a Platform from the Marketplace​

Audience: User

Description​

You can now hide a platform from the marketplace. In meshPanel, switch on "Hide in marketplace" in the general settings of the platform or when you register it. Via the meshPlatform API, set the new optional spec.availability.hiddenInMarketplace field. Use this when your users should order the platform through a building block definition instead, for example one that sets up a tenant on it, so the marketplace shows only the building block definition. Workspaces with access can still get tenants on a hidden platform. If you leave the field out of an API request, a new platform is shown in the marketplace and an existing platform keeps its current setting.

A Dedicated Permission to Approve Building Block Runs​

Audience: User

Description​

Approving or rejecting a building block run that waits for approval is now a permission of its own. Before, it came with the permission to change building blocks. You can now let an automation such as an AI agent change building blocks through an API key, while the decision on the runs those changes cause stays with a person. The meshObject API has a new action to reject such a run, and the meshStack CLI a new reject-run command. Admins and the platform team can still abort a run that waits for approval with the permission to change building blocks. This applies to meshPanel, the meshObject API and the meshStack CLI.

How to use​

We gave the new permission to every role and API key that could approve runs before, so nobody loses access. To keep the decision with a person, remove the permission to approve building block runs from the API keys your automations use. For an API key that should approve or reject runs, select it in the "Building Block Runs" group: the managed variant covers runs of building blocks whose definition your workspace owns, the admin variant covers all workspaces. If you manage API keys with the meshStack Terraform provider, the next apply removes the new permission from keys whose configuration does not list it. Add it, with a provider version that supports it, to the keys that should keep approving runs.

Workspace Members Can Read Usage Reports of Their Projects via API and CLI​

Audience: User

Description​

Workspace members can now list and read tenant usage reports through the meshObject API and CLI for all projects they are assigned to. Until now, tenants were only available via meshPanel and only Workspace owners or managers could read tenant usage reports via the API and CLI.

Workspace Members Can Read the Tenants of Their Projects via API and CLI​

Audience: User

Description​

Workspace members can now list and read tenants through the meshObject API and CLI for all projects they are assigned to. Until now, tenants were only available via meshPanel and only Workspace owners or managers could read tenants via the API and CLI.

Show Building Block Inputs Only on the Landing Zones That Need Them​

Audience: User

Description​

A condition on a building block input can now read a "Landing Zone Identifier" input. Use it to ask for an input only on the landing zones that need it, for example network settings only on a "networked" landing zone.

How to use​

Add an input with the source "Landing Zone Identifier" to a tenant-level building block definition, and give another input a condition that reads it by its input key, for example input.landing_zone == "networked".

Try Out a Landing Zone in the Building Block Configuration Preview​

Audience: User

Description​

When a building block definition has a "Landing Zone Identifier" input, the Configuration Preview next to the inputs now offers a field for it. Type a landing zone identifier there to see which inputs a user on that landing zone gets, before you publish the definition.

Create Projects and Tenants While Adding a Building Block​

Audience: User

Description​

In the "Add Building Blocks on One Page" feature preview, you can now create a project or a tenant right next to the project and tenant fields. Once it is created, the form selects it for you.

Building Blocks Show the Name of Their Payment Method Again​

Audience: User

Description​

When you open a Building Block, its payment method input now shows the name of the payment method again, instead of its raw identifier. You see this on the Overview and on the inputs page whenever you cannot edit the inputs. If the payment method is no longer available, we mark it as such, so you know it needs a replacement.

Organization Admins Can Manage Project Role Bindings with the meshStack CLI​

Audience: User

Description​

As an Organization Admin or Organization User, you can now manage the project role bindings of any project through the meshObject API and the meshStack CLI.

Audience: User

Description​

With the feature preview "Simplified project and tenant creation", a direct link to the Create Project or Create Tenant dialog now opens that dialog. Before, the dialog was lost.

Create a Tenant from an Empty Project​

Audience: User

Description​

On the workspace overview, a project without tenants used to show an empty card. If you manage the workspace, the card now offers to create a tenant in that project.

Newest Projects First on the Workspace Overview​

Audience: User

Description​

On the workspace overview, the projects you created recently appeared on top, but were sorted alphabetically. Now they are sorted newest first, so the project you have just created is always on top.

meshCommunication Target Uses the Standard Reference Shape​

Audience: User

Description​

The following two backwards-incompatible changes were made on the meshCommunication v1 (preview) API:

  1. The target (i.e., the workspace, building block or tenant) is now specified as spec.targetRef instead of spec.targetMeshObjectRef.
  2. If that target is a building block or tenant, then the UUID of that building block or tenant is specified via the uuid property, not the name property. That means spec.targetMeshObjectRef.name becomes spec.targetRef.uuid.

Four-Eyes Approval Now Also Applies to Role Bindings Made Through the API​

Audience: User

Description​

If your meshStack requires approval for role assignments, this now also applies to workspace and project bindings that you create through the meshObject API, for example with Terraform or the meshStack CLI. Before, an API key could grant any workspace or project role without a second approver. Now such a binding waits for approval in meshPanel, just like a role request made in meshPanel. The API key or API user that creates the request counts as the first approval, so a person in meshPanel gives the second one. API keys and API users with admin permissions still assign roles in other workspaces at once, like an admin in meshPanel. In the admin workspace, admin permissions do not work, as in meshPanel, and the API answers with 403. Only an API key of the admin workspace with the normal binding permissions can change bindings there, and a new binding needs approval. While four-eyes approval is on, only an Organization Admin can give an API key the permission to create workspace or project bindings.

How to use​

A binding that waits for approval is returned with "status.approval" set to "PENDING" and gives no access yet. Your workspace managers approve it in meshPanel, and then the binding becomes "ASSIGNED" under the name you chose. Deleting a pending binding withdraws the request. Bindings that only change the expiry date, and meshStacks without four-eyes approval, are not affected. API keys that already have the permission to create workspace or project bindings keep it. Please review these API keys. Workspace teams that manage bindings through the API now need an Organization Admin to give their API key this permission. See the 4 eye principle guide in our documentation for details.

Turn on the Platform Builder from the Marketplace​

Audience: User

Description​

You no longer need to find the Platform Builder switch in the workspace settings. If you manage a workspace that does not use the Platform Builder yet, the marketplace now shows a "Want to provide a service?" card at the end of the catalog. Click it and confirm, and we turn on the Platform Builder for your workspace and take you straight to its dashboard, where you can start offering your own services.

See Recent Usage Reports on the Tenant Details Page in the Admin Area​

Audience: User

Description​

The tenant details page in the admin area now shows the three most recent usage reports. You can see at a glance what a tenant costs, without searching the usage report list. "Show all" opens the usage report list, filtered to this tenant.

Clear Guidance When Marketplace Services Block Project Deletion​

Audience: User

Description​

When you want to delete a project that still has Marketplace service instances, the project deletion page now tells you so before you confirm. It lists each service instance with a link to the page where you can delete it. Once you have deleted them, come back and delete the project.

Before, you only saw a technical error after you confirmed the deletion, which named a tenant and "OSB Service Instances". If you delete a project via the API, the error message now uses the same plain wording.

Unused Built-in Platform Types Are Deactivated With Lightweight Platforms​

Audience: User

Description​

When you turn on "Lightweight Platforms" in the meshStack settings, we now deactivate every built-in platform type that no active platform and no building block definition uses. You no longer see them when you create a platform or pick the supported platforms of a building block definition. Built-in platform types that are in use stay active. When you turn the setting off, we activate those platform types again. Platform types that you deactivated yourself stay deactivated.

Find the Default Building Block Runner in the API​

Audience: User

Description​

The API now marks which building block runner is the default. The default runner is managed by meshStack.

Platform Settings Reject an Empty Tag Prefix​

Audience: User

Description​

meshStack now rejects a platform configuration whose tag configuration has an empty tag prefix. This applies to the platform settings in the admin area and to the meshPlatform API. With an empty prefix, meshStack treats every tag on a tenant as its own and deletes the tags that it did not create, including tags that you manage with your own tooling. Existing platform configurations are not changed.

How to use​

Enter a tag prefix, for example "meshstack_". If you do not want meshStack to manage tags at all, remove the tag configuration instead. In the meshPlatform API, send no tag configuration (null).

Switch Off Tag Replication for a Platform​

Audience: User

Description​

You can now remove the tag configuration of an AWS, Azure, Azure Resource Group, GCP or OpenShift platform in the platform settings. Without a tag configuration, meshStack does not create, change or delete any tags or labels on the tenants of this platform, so tags that you manage with your own tooling stay untouched. Before, you could not save the settings of a platform that had no tag configuration.

How to use​

In the replication settings of the platform, click "Remove Tag Configuration" and save. To let meshStack manage tags again, click "Add Tag Configuration" and enter a tag prefix. meshStack only manages tags whose key starts with this prefix.

See When and by Whom a Communication Was Created via the API​

Audience: User

Description​

The meshCommunication API (preview) now returns the lifecycle of each communication in status.lifecycle, like the other meshObjects do. You see its lifecycle state, when it was created, and whether a user, an API key or meshStack itself created it. This helps you audit which automation or person sent a communication to an application team.

Kind Is Now Required in the Communication Definition Reference​

Audience: User

Description​

When you create a communication through the meshCommunication API (preview), the request body references a communication definition in the field spec.communicationDefinitionRef. This reference now must contain the field kind with the value meshCommunicationDefinition, next to the uuid of the definition. Before, the API added a missing kind for you. Now it rejects such a request with a 400 error. If your automation sends the reference without kind, add it to keep creating communications.

Undelete a Building Block Whose Deletion Failed​

Audience: User

Description​

A building block whose destroy run fails, for example because its Terraform code uses prevent_destroy, stays marked for deletion, and every further run tries to destroy it again. The platform team that owns the building block definition can now undelete such a building block in meshPanel or with POST /api/meshobjects/meshbuildingblocks/{uuid}/undelete. Afterwards the building block is no longer marked for deletion and runs like any other building block, and its event log shows "Building Block Undeleted". Undelete is refused while a deletion run is pending or in progress, and while the tenant or the building block definition is being deleted.

See Which Projects Miss a Payment Method in the Workspace Overview​

Audience: User

Description​

The workspace overview now shows you which projects have no payment method, so you can fix them in one click. Each affected project shows "No payment method" next to its users and costs. It takes you straight to the page where you assign one. A red "Projects without Payment Method" card at the top shows how many projects are affected; click it to list only those projects.

These replace the long yellow warning that we showed above every workspace page. You see them if you can manage the workspace and payment methods are enabled in your meshStack.

Security Fix: Authorization Issue (SA-2026-02)​

Audience: User

Description​

We fixed an authorization issue in meshStack. No specific action is required: upgrade at your next maintenance window as usual. meshStack SaaS customers receive this fix automatically. See security advisory SA-2026-02 for details: https://feedback.meshcloud.io/knownissues/

Simplified Tenant Creation​

Audience: User

Description​

With the feature preview "Simplified project and tenant creation", "Create Tenant" now also opens one dialog right where you are instead of the step-by-step wizard. To try it, select "Try the new experience" in the Create Tenant wizard.

New Tenants First on the Project Tenants Page​

Audience: User

Description​

The tenants page of a project now shows a tenant right after you create it, and lists the tenants created recently first, the newest on top.

General Availability for the meshBuildingBlock v2 API​

Audience: User

Description​

The meshBuildingBlock v2 meshObject API is now generally available (v2). It is stable and ready for production use, and further changes follow the standard GA versioning process. Clients that still send the v2-preview media type keep working: meshStack answers them with the GA version.

General Availability for the meshBuildingBlockDefinition v1 API​

Audience: User

Description​

The meshBuildingBlockDefinition and meshBuildingBlockDefinitionVersion meshObject APIs are now generally available (v1). They are stable and ready for production use, and further changes follow the standard GA versioning process. Clients that still send the v1-preview media types keep working: meshStack answers them with the GA version.

Admins Can Delete a Tenant from the Admin Area​

Audience: User

Description​

You can now delete a tenant from its Settings tab in the admin area, with the new "Delete Tenant" option next to "Purge Tenant". Unlike a purge, this starts the regular tenant deletion: we delete the building blocks of the tenant and then the tenant itself, as configured for its platform. As you start the deletion as an admin or platform operator, we approve it right away and it does not wait for a separate approval. To confirm the deletion, you enter the project identifier.

Tag Selections Show the Same Name in the List and the Field​

Audience: User

Description​

When you pick a value for a single-select or multi-select tag, the dropdown list now shows the same text as the field after you select it. Before, the list showed only the tag value identifier, while the field showed its display name, so it was hard to find the option you wanted.

Where a display name differs from its identifier, you now see both, for example "Research & Development (research-and-development)". You can also search the list by either of them. This applies to every single-select and multi-select tag field in tag forms, for example on workspaces, projects and payment methods.

Send Platform Notification Mails to a Team Mailbox​

Audience: User

Description​

You can now send platform notification mails to a team address. For example, an AWS platform team can use the shared address aws-platform-team@company.org and receive a mail when the replication of an AWS tenant failed.

As an Organization Admin, you find the new page under Platforms > Mailbox Notifications in the admin area. For each mailbox you choose which of these mails it gets: Tenant Marked for Deletion, Tenant Quota Request, New Tenant Created and Tenant Replication Failed. You also choose the platforms it gets them for. A platform type covers all of its platforms, also the ones you add later. A single platform covers only this platform.

Move Tenant Wizard Only Warns About Policy Violations a Move Would Cause​

Audience: User

Description​

When you move a tenant in the admin area, the review step now checks the policies against the destination project and its workspace before you confirm. You only see a policy violations warning when the move would actually violate a policy, and the warning names those policies. Before, the review step always showed a policy violations notice, which made it look like something was already wrong.

Screen Readers Read the Wizard Button as It Is Shown​

Audience: User

Description​

Screen readers announced the button that moves a wizard to its next step as "Submit", whatever the button showed. They now read its visible text, for example "Next" or "Create Platform".

Platform Types List Shows Active Platform Types by Default​

Audience: User

Description​

The platform types list in the admin area now shows only active platform types when you open it. To see deactivated platform types, for example to reactivate one, choose "Deactivated" or "All" in the status filter.

Improved Workspace Isolation for Building Blocks in the meshObject API​

Audience: User

Description​

We improved workspace isolation when you use the meshObject API with user authorization. A user token is issued for one workspace. Before, if you were a member of projects in several workspaces, a token issued for one of them also let you update tenant building blocks, trigger their runs and abort their runs in your other workspaces. Now meshStack only accepts building blocks of the workspace that the token is issued for. To manage a building block of another workspace, use a token issued for that workspace.