Skip to main content

Release 2026.16.0

· 9 min read
meshcloud

Release period: 2026-04-08 to 2026-04-15

This release includes the following issues:

  • Deprecated Platforms No Longer Selectable for New Tenants
  • Fixed Building Block Runs Getting Stuck in Rare Cases
  • Fix Table Overflow Across All Tables
  • Fix Workspace Services Sorting by Workspace
  • Fix for Workspace Building Blocks Requiring Tenant Selection
  • Default Tag Value Not Applied to Single-Select Workspace Tags
  • More Fields Supported When Importing Building Block Definitions
  • Fix Concurrent Landing Zone Creation Failures
  • Fix CODE Input Editor not Rendering in Building Block Upgrade
  • Improved Security for Building Block Runs Using Ephemeral Tokens
  • All Platform Types Now Visible When Creating a Platform Instance
  • Improved Building Block Triggering for More Efficient Event Processing
  • Access Request Reason Column Text Wrapping
  • Improved Tenant Replication Reliability
  • Improved Author Display in Event Log for All Historical Events
  • Improved Error Responses for Binding Import Validation
  • Validate Building Block Target Type Matches Target Reference
  • Platform Builder Dashboard Cards Sorted by Last Modification Date
  • Fix Empty Building Block Runner Changed Events
  • Renaming a Building Block Definition Output No Longer Breaks Child Inputs
  • Validation of Sensitive CODE Type Inputs in Building Block Definitions
  • Automatic Name Suggestions for Building Block Creation
  • Fix Group-based Permissions for building block User Permissions Input

Ticket Details​

Deprecated Platforms No Longer Selectable for New Tenants​

Audience: User

Description​

We fixed a bug where deprecated platforms were still visible and selectable when creating new tenants or projects, and remained visible in the marketplace catalog. This contradicted the documented behavior that deprecation prevents further tenant creation.

Deprecated platforms are now correctly hidden from the marketplace, tenant creation wizards, and project creation flows. Attempting to create a tenant on a deprecated platform via the API is also rejected. Existing tenants on deprecated platforms remain unaffected.

Fixed Building Block Runs Getting Stuck in Rare Cases​

Audience: User

Description​

We fixed an issue where Building Block runs could get stuck in an "in progress" state indefinitely without ever being executed. Previously, aborting these stuck runs was also not possible. Both issues are now resolved - runs will no longer get stuck, and can be properly aborted if needed.

Fix Table Overflow Across All Tables​

Audience: User

Description​

We fixed a widespread display bug where tables throughout the admin and user area would overflow their containers on smaller screens or when many columns were shown. This caused broken horizontal scrollbars that spanned the entire page, making content hard to read and navigate. All tables now scroll horizontally within their own containers, keeping the rest of the page layout intact.

Fix Workspace Services Sorting by Workspace​

Audience: User

Description​

When sorting the workspace services table by workspace, the page failed to load with an internal error. We fixed this so you can now sort workspace services by workspace without issues.

Fix for Workspace Building Blocks Requiring Tenant Selection​

Audience: User

Description​

We fixed a regression where deploying a workspace building block from the platform builder always showed a tenant selection dropdown, even though workspace building blocks do not require a tenant.

Default Tag Value Not Applied to Single-Select Workspace Tags​

Audience: User

Description​

When creating a new workspace, single-select workspace tags with default values were not being pre-populated correctly. If the default value's name contained a substring that matched another tag option, the wrong option would be selected instead. For example, with options "dev", "dev-restricted", and a default of "dev-restricted", the tag would incorrectly pre-fill with "dev".

More Fields Supported When Importing Building Block Definitions​

Audience: User

Description​

When importing a building block definition from meshStack Hub, we now prefill more fields from the Terraform configuration and apply sensible defaults for the fields missing from the configuration.

Fix Concurrent Landing Zone Creation Failures​

Audience: User

Description​

We fixed a race condition that could cause concurrent landing zone creation requests to fail with HTTP 500 errors. This issue affected landing zones with mandatory building blocks when using OpenTofu or other tools to create multiple landing zones on the same platform simultaneously. The system now properly serializes these requests to prevent conflicts and ensures all landing zones are created successfully.

Fix CODE Input Editor not Rendering in Building Block Upgrade​

Audience: User

Description​

We fixed a bug where the text editor for CODE-type inputs was not rendered during building block upgrades when the input was newly added in the target version. This prevented users from entering required values, making the upgrade impossible to complete.

Improved Security for Building Block Runs Using Ephemeral Tokens​

Audience: User

Description​

We improved the authentication mechanism for building block Terraform runs. The runner now uses a short-lived, per-run ephemeral token instead of long-lived credentials, reducing the security exposure of each run.

If you use the meshStack-managed Terraform HTTP backend, OpenTofu 1.7.2 or later is required to support this change.

All Platform Types Now Visible When Creating a Platform Instance​

Audience: User

Description​

When creating a new platform instance, you can now see and browse all available platform types. Previously, the list was limited to the first 50 entries, which could hide platform types if many were configured.

Improved Building Block Triggering for More Efficient Event Processing​

Audience: User

Description​

We improved the internal handling of building block run triggers. Building block runs are now triggered more efficiently. This reduces the risk of stale or inconsistent data being used during building block runs and makes the overall triggering more resilient.

Access Request Reason Column Text Wrapping​

Audience: User

Description​

The "Reason" column in the Access Requests table on the Admin Access Control page now properly wraps long text instead of overflowing horizontally. This improves readability and ensures all access request details are visible within the table layout.

Improved Tenant Replication Reliability​

Audience: User

Description​

We improved the internal mechanism used to trigger tenant replication. The new approach prevents data inconsistencies and race conditions that could previously cause tenant replications to temporarily fail in rare cases.

Improved Author Display in Event Log for All Historical Events​

Audience: User

Description​

The event log now shows a meaningful author display for all events, including older ones. Previously, the improved author column (with an icon indicating the author type (user, API key, or system) and a readable name) was only visible for events created after November 2025. Older events showed a cryptic UUID instead. We've extended this improvement so that all events, regardless of when they were created, now benefit from the same clear and informative author display. You can also hover over the author icon to see a tooltip with the author type.

Improved Error Responses for Binding Import Validation​

Audience: User

Description​

The meshObject API now returns 400 Bad Request instead of 500 Internal Server Error when importing workspace or project bindings that reference a non-existent workspace, role, or project. This makes it easier to diagnose and fix invalid binding import requests.

Validate Building Block Target Type Matches Target Reference​

Audience: User

Description​

The meshObject API now returns 400 Bad Request when creating a building block whose targetType (e.g. meshTenant or meshWorkspace) does not match the provided target reference. Previously, inconsistent target information was accepted and could cause errors during processing.

Platform Builder Dashboard Cards Sorted by Last Modification Date​

Audience: User

Description​

The dashboard now shows building block definitions and platforms sorted by last modification date, with the most recently changed items appearing first. This makes it easier for you to quickly see what's been updated at a glance, without having to search through an alphabetical list.

Fix Empty Building Block Runner Changed Events​

Audience: User

Description​

Previously, meshStack emitted a "building block runner changed" event every time a building block runner was updated via the API - even when nothing actually changed. This meant the event log showed change entries with no visible diff. We fixed this so that meshStack now skips the event entirely when the runner configuration is identical to what was already stored.

Renaming a Building Block Definition Output No Longer Breaks Child Inputs​

Audience: User

Description​

When you renamed an output of a parent building block definition which is in draft state, any child building block definition in draft state that had an input referencing that output would silently lose its connection. You had to manually find and fix the broken input reference. This relation now updates automatically.

Validation of Sensitive CODE Type Inputs in Building Block Definitions​

Audience: User

Description​

We extended the input validation for building block definition versions to also cover sensitive inputs of type CODE. When providing a sensitive CODE input via the API, the plaintext value must be a plain string. If you pass a raw JSON object instead, the API now returns a clear error message explaining what went wrong. Please refer to our API documentation for details on the correct format.

Automatic Name Suggestions for Building Block Creation​

Audience: User

Description​

When you create a new building block and a block with the same name already exists in the same workspace or tenant, meshStack now automatically suggests a unique name for you - for example, "My Block (1)" or "My Block (2)". The name field switches into edit mode so you immediately see the suggestion and can adjust it further before deploying.

Fix Group-based Permissions for building block User Permissions Input​

Audience: User

Description​

This fixes a bug where building blocks using the "User Permissions" input type were not re-triggered in all affected workspaces when a user was disabled or enabled (e.g. via SCIM).

Previously, building blocks were only re-triggered in workspaces where the user had a direct binding. If the user's access came via group membership, those workspaces were silently skipped - so those building blocks kept running with outdated permission data until the next unrelated change in that workspace.

How to use​

Building blocks that use the "User Permissions" input type will automatically receive updated role data the next time a user in the affected workspace is disabled or enabled. You can also trigger any affected building block manually to apply the correct data immediately.