Skip to main content

Release 2026.22.0

· 6 min read
meshcloud

Release period: 2026-05-20 to 2026-05-27

This release includes the following issues:

  • Fix Dropdowns for Inputs during Building Block Upgrade
  • Building Block Runs View Refreshed to a Table
  • Track and Display Building Block Runner Versions
  • meshServiceInstance API now exposes the Service Broker Identifier
  • Enhanced Workspace Welcome Experience with Featured Services
  • Delete Button for All Runners Now Works Correctly in the Admin Area
  • Building Block Definition Target References Updated in meshObject API
  • Unified Building Block Overview with Improved Search
  • AWS Account Alias No Longer Applied During Replication
  • Removal of meshIdB IAM Type for AWS Platforms

Ticket Details​

Fix Dropdowns for Inputs during Building Block Upgrade​

Audience: User

Description​

When upgrading a building block that requires single-select or multi-select inputs not yet set, you now see a proper dropdown with the available options in the panel instead of a free-text field.

Building Block Runs View Refreshed to a Table​

Audience: User

Description​

We refreshed the building block runs view to use a table, so it's consistent with other run views in meshStack. You can now filter runs by status or run type (dry run vs. regular run) to quickly find what you're looking for. The table also shows whether each run was a dry run or a regular run.

Track and Display Building Block Runner Versions​

Audience: User

Description​

meshStack now tracks the version of each building block runner whenever it reports for work. We display the last known version in the runner details page and the runner overview table, making it easy for you to verify that your runners are up to date.

meshServiceInstance API now exposes the Service Broker Identifier​

Audience: User

Description​

The meshServiceInstance v2 API now includes the service broker identifier in the response. You can use this field to identify which service broker is managing a given service instance without having to perform additional lookups. You can also filter the list of service instances by service broker identifier using the new serviceBrokerIdentifier query parameter.

Audience: User

Description​

The workspace overview welcome state now displays featured services when available, making it easier for new users to discover and access the most relevant resources for their workspace. The redesigned welcome screen prominently showcases featured services alongside quick links to browse the full marketplace and create projects.

Delete Button for All Runners Now Works Correctly in the Admin Area​

Audience: User

Description​

We fixed a bug where the delete button in the admin area was incorrectly hidden for runners that belonged to other workspaces. Admins can now delete any custom runner regardless of which workspace owns it. Runners shipped with meshStack are protected and will continue to show a lock icon instead.

Building Block Definition Target References Updated in meshObject API​

Audience: User

Description​

We updated how you reference targets when creating building blocks via the meshObject API. Since meshBuildingBlock is still in preview, we made this breaking change to align target references with the standard meshObject API conventions. This ensures consistency across the API as the feature matures.

How to use​

For tenant-scoped building blocks, use uuid to identify the target tenant:

"targetRef": {
  "kind": "meshTenant",
  "uuid": "<tenant-uuid>"
}

For workspace-scoped building blocks, use name to identify the target workspace:

"targetRef": {
  "kind": "meshWorkspace",
  "name": "<workspace-identifier>"
}

The previously accepted identifier field is no longer supported in targetRef.

Audience: User

Description​

We consolidated the building block overview into a single table with fewer columns for a better overview. Tenant-level and workspace-level building blocks now appear together, giving you one place to manage everything.

Search also got better: a new combined column allows you to search building blocks over name, definition name, definition version and the corresponding UUIDs. Another new hierarchy column lets you filter by workspace, project, and platform using names, identifiers and UUIDs. You can also filter by multiple statuses at the same time.

All search fields accept multiple terms separated by spaces or commas - results will match all of them.

AWS Account Alias No Longer Applied During Replication​

Audience: User

Description​

meshStack no longer sets or manages AWS account aliases during replication. The "Account Alias Pattern" and "Enforce Account Alias" configuration fields still exist in the API and are persisted for backward compatibility with existing configurations (e.g., Terraform provider). However, their values are ignored - meshStack will not create, update, or enforce account aliases on AWS accounts. These values were intended for an old removed IdB flow. As account aliases need to be unique across AWS, the removal of these fields increases project name reusability.

How to use​

If you relied on meshStack to set AWS account aliases, you will need to manage account aliases yourself going forward. Existing account aliases on your AWS accounts are not affected by this change - meshStack will simply stop updating them.

If you use the Terraform provider or manage platform configuration via the meshObject API, your existing configurations remain valid. The fields accountAliasPattern and enforceAccountAlias can still be submitted and will be accepted, but their values will have no effect on replication behavior.

Removal of meshIdB IAM Type for AWS Platforms​

Audience: User

Description​

We have removed the meshIdB IAM type for AWS platform integration from meshStack. This integration type used the meshStack-internal identity provider (Keycloak / meshIdB) as a SAML IdP for AWS IAM, and was previously deprecated.

All AWS platforms must now use either the AWS IAM Identity Center (SSO) or the AWS Identity Store API integration type. If your platform was still configured with the meshIdB type, meshStack will automatically remove the obsolete configuration. Please reconfigure your platform to use one of the supported IAM types.

We recommend migrating to the AWS Identity Store API integration, which supports Workload Identity Federation (WIF) and does not require a long-lived SCIM token. For further details, see the deprecation notice.