Skip to main content

Release vNext

· 5 min read
meshcloud

Release period: 2026-07-23 to 2026-07-23

This release includes the following issues:

  • Status and Action Column in the Building Block List
  • Clear Error When an Input Key Clashes With a Reserved System Key
  • Building Block Outputs Now Respect the Configured Display Order
  • Deleted Tenants Are Now Part of the Tenants Screen
  • Fixed Incorrect List Item Rendering in the meshObject API Documentation
  • Workspace Bindings API Now Exposes and Accepts an Expiry Date
  • Filter Platforms by Type in the API
  • Discover Landing Zones of Platforms Published to You via the API
  • Discover Platforms Published to Your Workspace via the API

Ticket Details​

Status and Action Column in the Building Block List​

Audience: User

Description​

The Building Block list now separates the status of a Building Block from the work it currently requires. A dedicated Status column shows at a glance whether the latest apply or destroy run of a Building Block succeeded, failed, or deleted its resources, along with how long ago that latest run started. The former status column is replaced by an action column that tells you what to do next (provide input, review errors, or upgrade to the latest Building Block Definition version) and links straight to where you can act on it. You can also filter the list by status and by required action.

The action column also reflects dry runs: a pending or running dry run shows up as "Dry run #N", and a failed dry run surfaces as "Review Errors" - without the dry run affecting the Building Block's status or health. A succeeded dry run that detected drift surfaces as "Review Drift", so you can spot Building Blocks whose real state has diverged from their definition. You can also filter the list by this action.

Clear Error When an Input Key Clashes With a Reserved System Key​

Audience: User

Description​

When you create or edit a Building Block Definition, meshStack automatically adds reserved system inputs such as MESHSTACK_ENDPOINT and MESHSTACK_API_TOKEN. If one of your own input keys matched a reserved key, even when it only differed in capitalisation like meshstack_endpoint, the save failed with a confusing internal error.

You now get a clear message telling you the key is reserved, both directly in the Panel form as you type and when saving. We also detect duplicate input keys that differ only in case, matching how meshStack stores them.

Building Block Outputs Now Respect the Configured Display Order​

Audience: User

Description​

When you configure a display order for the outputs of a Building Block Definition, we now show those outputs in that exact order on the Building Block detail page and in the resource links on the Building Block card. Previously these two views ignored the configured order and listed outputs in the order they happened to be produced, so reordering them had no visible effect there. This gives you full, consistent control over how outputs appear to your users.

Deleted Tenants Are Now Part of the Tenants Screen​

Audience: User

Description​

Deleted tenants now show up directly in the Tenants screen of the admin area and the platform builder with their own "Deleted" status. You can filter for them via the status filter, and you can approve or decline pending tenant deletion requests right from the list. The separate "Deleted Tenants" view is retired; its sidebar entry now guides you to the new location.

Fixed Incorrect List Item Rendering in the meshObject API Documentation​

Audience: User

Description​

List endpoints in the meshObject API documentation (such as projects, tenants, workspaces, building blocks and communications) rendered the items of a paged response as a confusing mix of every possible type, and the generated examples were invalid. Each list item now documents its full set of fields, just like the corresponding single-object endpoint.

Workspace Bindings API Now Exposes and Accepts an Expiry Date​

Audience: User

Description​

The meshObject API for workspace user bindings and workspace group bindings now includes the expiry date of a binding. When you read a binding, you can see when its role assignment expires. When you create a binding, you can set an expiry date directly.

Filter Platforms by Type in the API​

Audience: User

Description​

The meshPlatform list API now supports a platformTypeIdentifier filter so you can list only platforms of a given platform type through the API, making it easy to find compatible platforms of a specific type.

Discover Landing Zones of Platforms Published to You via the API​

Audience: User

Description​

The meshLandingZone API now also returns the Landing Zones of platforms another workspace has published to yours, so an API key with read access can resolve a compatible Landing Zone for a published Platform through the API, not just for platforms you own or contribute to.

Discover Platforms Published to Your Workspace via the API​

Audience: User

Description​

The meshPlatform API now also returns platforms another workspace has published to yours, not just those you own or contribute to, so an API key with read access can discover and reference them instead of hard-coding a UUID. When you only consume a published platform its technical connection configuration is omitted (the owning workspace and admins still receive it); secrets are always returned as hashes.