Skip to main content

Release 2026.45.0

· 13 min read
meshcloud

Release period: 2026-10-28 to 2026-11-04

This release includes the following issues:

  • Download ready-to-use building block code snippets from the marketplace
  • Terraform Provider No Longer Ends Building Block Updates Too Early
  • Fix Workspace List Collapsing When Importing an Unmanaged Tenant
  • Clearer Workspace and Project Names When You Move a Tenant
  • Project Tags Wrap onto Multiple Lines in the Project Header
  • GitHub, GitLab and Azure DevOps Integrations Are No Longer Labelled Beta
  • Preview endpoint GET /api/meshobjects/meshapikeys/self is removed
  • Event Log Shows When a Platform Type Is Created
  • Choose Platforms Instead of a Type for Building Block Definitions
  • Admin Dashboard Counts Match the Building Block List
  • Pages Keep Their Scroll Position When a Modal Opens and Closes
  • Clear Error for a Platform Web Console URL Over 200 Characters
  • Run meshStack Without Tenant Replication
  • Create Your First Project From the Workspace Overview
  • See When and by Whom a Communication Definition Was Created via the API
  • Lightweight Platforms Setting to Allow Only Custom Platforms
  • Let AI Agents Manage Building Blocks for You
  • Your meshStack Serves the OpenAPI Specifications of Its APIs
  • Reliable Waiting for Building Block Runs Through the API
  • Tenant Creation Checks Permissions of Every Building Block It Creates
  • Quota Definitions Only on Platforms That Apply Quotas
  • Communications Show Whether a User or an API Key Sent Them
  • Trigger Replication Only Shows When You May Replicate the Tenant
  • Status Badges Stay Visible for Long Tenant Names on the Workspace Overview
  • Align the Dependencies of Building Blocks with Their Draft Definition
  • Fixed Duplicate Audit Events for SCIM Group Membership Changes
  • Fixed Failing SCIM Group Updates When Members Are Removed and Added Back
  • Budget Alerts Go Only to Current Workspace Managers and Owners

Ticket Details​

Download ready-to-use building block code snippets from the marketplace​

Audience: User

Description​

You can now copy/download a ready-to-use OpenTofu/Terraform code snippet to order a building block from the marketplace. In your workspace, go to Marketplace, open a building block and click "Add as code".

Terraform Provider No Longer Ends Building Block Updates Too Early​

Audience: User

Description​

When tofu apply updated a building block, the meshstack Terraform provider could report the update as finished while the building block's run had only just started. Resources that read the building block's outputs in the same apply then still got the old values. If you check status.succeeded in a postcondition, the next plan failed with "did not succeed (health status SUCCEEDED, action PENDING)" until the run had ended. We fixed how meshStack reports a building block while a new run starts, so the provider now waits until the run has really ended. You do not need to upgrade the provider.

Fix Workspace List Collapsing When Importing an Unmanaged Tenant​

Audience: User

Description​

When you assign an unmanaged tenant to a project, you can now see all workspaces that match your search. Before, the workspace list could shrink to a thin empty bar as you typed, so you could not select the workspace you searched for.

Clearer Workspace and Project Names When You Move a Tenant​

Audience: User

Description​

When you move a tenant, we now show "Name:" in front of the name of the current workspace and project, next to the identifier. You can now see at a glance which value is the name and which is the identifier.

Project Tags Wrap onto Multiple Lines in the Project Header​

Audience: User

Description​

When you expand all tags of a project with "Show more", the tags in the project header now wrap onto multiple lines. Before, they stayed on one line, so long or many tags ran off the screen and you had to scroll sideways to read them.

GitHub, GitLab and Azure DevOps Integrations Are No Longer Labelled Beta​

Audience: User

Description​

The GitHub, GitLab and Azure DevOps integrations for Building Block Definitions are generally available. We removed the outdated BETA labels from the implementation settings and from the Azure DevOps option when you create a new Building Block Definition.

Preview endpoint GET /api/meshobjects/meshapikeys/self is removed​

Audience: User

Description​

We removed the preview endpoint GET /api/meshobjects/meshapikeys/self. It now answers 404, like every other method on this path.

The meshStack CLI before v0.9.0 shows a warning in meshstack auth status and no longer shows the details of the API key. Update the meshStack CLI to v0.9.0 or later.

Event Log Shows When a Platform Type Is Created​

Audience: User

Description​

When someone creates a custom platform type, we now write an entry to the event log. You can see who created the platform type and when, just like you already can for deactivating and reactivating it.

Choose Platforms Instead of a Type for Building Block Definitions​

Audience: User

Description​

When you create a building block definition, you no longer choose between "Workspace Building Block" and "Tenant Building Block". You only choose the platforms it builds on. If you choose none, it lives on workspace level. With at least one platform, it lives on platforms and can be added to tenants of those platforms.

How to use​

You pick platforms in a list grouped by platform type, which you can search. Tick a platform type to include all of its platforms, also the ones added later, or open it and tick single platforms. Choosing workspace level again clears your choice. Existing building block definitions keep their level.

Admin Dashboard Counts Match the Building Block List​

Audience: User

Description​

The "Building Blocks requiring approval" and "Building Blocks requiring operator input" counts on the admin dashboard now match the building block list that their links open. Before, they could show a higher number than the list.

The dashboard also shows a new count, "Building Blocks with errors to review".

Pages Keep Their Scroll Position When a Modal Opens and Closes​

Audience: User

Description​

When you scroll down a long page and open a modal, the page no longer moves under the backdrop. After you close the modal, you stay exactly where you were instead of jumping back to the top.

Clear Error for a Platform Web Console URL Over 200 Characters​

Audience: User

Description​

A platform web console URL can have at most 200 characters. When you create or update a platform with a longer URL through version v2 of the meshPlatform API, or save a longer URL in the general settings of a platform, meshStack now rejects it with an error that names the field and the 200 character limit. Before, the request failed with an internal server error.

Run meshStack Without Tenant Replication​

Audience: User

Description​

If you build all your platforms with building blocks, your meshStack can now run without tenant replication. meshStack then answers the replication of every tenant on a custom platform itself: the tenant succeeds as soon as one of its building blocks reports the platform tenant ID. Such a meshStack can also run without metering and billing, so it creates no usage reports and no chargeback statements, and meshPanel hides the financial reports in the platform builder and the cost cards of every workspace and project. When payment methods are disabled as well, meshPanel also hides the financials tab of every workspace.

The failed tenants and the open quota requests on the admin dashboard now count exactly the tenants that the tenant list shows when you follow the link.

Create Your First Project From the Workspace Overview​

Audience: User

Description​

When your workspace already had workspace building blocks but no project yet, the workspace overview showed no way to create a project. You now see the projects section with its "Create Project" button there as soon as you can manage the workspace, so you can create your first project without going through the marketplace.

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

Audience: User

Description​

The meshCommunicationDefinition meshObject API now returns the lifecycle of each communication definition, 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 your application teams.

Lightweight Platforms Setting to Allow Only Custom Platforms​

Audience: User

Description​

If you build all your platforms with building blocks, you can now turn on "Lightweight Platforms" in the meshStack settings. While it is on, meshPanel and the API only create platforms of a custom platform type and refuse new mandatory or recommended building blocks on landing zones of custom platforms. meshPanel also hides those building blocks and the "Configuration" tab of custom platforms. Platforms, landing zones and building blocks you already have keep working.

Let AI Agents Manage Building Blocks for You​

Audience: User

Description​

You can now hand building block work to an AI agent, such as the coding assistant in your IDE. Point it at docs.meshcloud.io/llms.txt and it finds everything it needs: how to log in as you, the rules it must follow, and step-by-step tasks to create, release and manage building block definitions and building blocks. When you have no CLI login yet, the CLI Logins page now shows how to install the meshStack CLI and log in. This hint, which the API keys page shows as well, names the link for AI agents.

How to use​

See "How to Work With AI Agents" in the getting started section of our documentation.

Your meshStack Serves the OpenAPI Specifications of Its APIs​

Audience: User

Description​

You can now download the OpenAPI specifications of the meshStack API and the metering API from your meshStack itself, at /api/openapi of each API, without logging in. They always describe the APIs your meshStack runs right now, so clients and code generators you point at them never see endpoints or versions your meshStack does not have yet.

Reliable Waiting for Building Block Runs Through the API​

Audience: User

Description​

When your API client updates a building block or triggers a run, it can now tell reliably when that run has started. While meshStack waits to start the run, it starts no scheduled drift detection or drift reconciliation run on the building block, and it rejects a dry run trigger, in the API and in meshPanel, with 409 Conflict. Before, such a dry run could start in this time, and a client could take it for the run it was waiting for.

How to use​

The building block documentation explains in the section "Waiting for a Run" which status fields to compare.

Tenant Creation Checks Permissions of Every Building Block It Creates​

Audience: User

Description​

When you create a tenant, we now check that you hold the API permissions declared by every building block created with it, including the mandatory ones of the landing zone. Adding a building block to an existing tenant already worked this way. Workspace owners and managers hold almost all permissions a definition can declare, so this rarely affects anyone. API keys that create tenants need the declared permissions as well.

Quota Definitions Only on Platforms That Apply Quotas​

Audience: User

Description​

meshStack applies quotas only on OpenStack, Cloud Foundry, OpenShift, Kubernetes and Azure Kubernetes Service platforms. The meshPlatform API now refuses quota definitions with a new quota key on any other platform, for example a custom platform, because tenants of such a platform would get quotas that are never applied.

Communications Show Whether a User or an API Key Sent Them​

Audience: User

Description​

The communication center and the communications of a workspace now show who sent a communication with the same author display that you know from building block runs and API keys. You see whether a user, an API key or meshStack itself created the communication, with an icon and the name. Before, communications that an API key created showed an internal audit user instead of the API key. When the sending user has been deleted, we show their identifier instead of their name.

The "Created By" and "Sender" search now finds a communication by the name that the column shows, whether a user, an API key, an API user or meshStack itself created it. Before, the search only matched the names of users. You can no longer sort by these two columns, because these kinds of creators have no common name to sort by.

Trigger Replication Only Shows When You May Replicate the Tenant​

Audience: User

Description​

On the admin tenant details page, you now only see the "Trigger Replication" button when you are allowed to replicate that tenant. Before, everyone saw it, and clicking it failed for users without the permission to replicate tenants.

Status Badges Stay Visible for Long Tenant Names on the Workspace Overview​

Audience: User

Description​

On the workspace overview, a tenant with a long name, such as an Azure resource group ID, no longer pushes its NEW, Deletion Pending or Deletion Failed badge out of the card. You now always see the badge, and the name ends with "..." when it does not fit on two lines.

Align the Dependencies of Building Blocks with Their Draft Definition​

Audience: User

Description​

When you add or remove a dependency on a draft building block definition, its building blocks can now follow without a new version. In meshPanel, open the building block and go to Settings > Dependencies, or use the Edit link on the Dependencies card of its overview. Through the meshObject API, change the parent building blocks of the building block with a PUT that keeps its version. This works only if the building block is on a draft version. Each building block you choose must be of a definition the version depends on, one per dependency. A platform operator or admin makes the change, and meshStack then runs the building block once.

Fixed Duplicate Audit Events for SCIM Group Membership Changes​

Audience: User

Description​

When your identity provider sent several SCIM group requests at the same time, meshStack could process the same group membership change twice, and you saw its audit event twice in the event log. We now process each membership change that arrives via SCIM exactly once.

Fixed Failing SCIM Group Updates When Members Are Removed and Added Back​

Audience: User

Description​

When your identity provider removed members from a group and added them back shortly after, meshStack could run into a database deadlock while it processed these changes. Then either our background processing of the group change failed and started again one minute later, or the SCIM request failed and your identity provider had to retry it. Until then, the event log entries, building block runs and replication of the new membership were missing. We removed the cause of this deadlock.

Budget Alerts Go Only to Current Workspace Managers and Owners​

Audience: User

Description​

We now send budget alerts only to the people who are workspace managers or workspace owners at the time we send the mail. Before, people who had lost this role could keep getting these mails.