Skip to main content

Release 2026.20.0

· 5 min read
meshcloud

Release period: 2026-05-06 to 2026-05-13

This release includes the following issues:

  • Improved Runner Detail and Create Pages with a Context Header
  • Improved Compatibility for Building Block Dependencies
  • Improved Reliability When Sending Updates to Deletion Runs
  • Improved Runner Creation and Management in the Platform Builder
  • Public Key Generation Guide in Building Block Runner Creation
  • Fixed Date Selectors Being Cut Off in Tables
  • Metering Status No Longer Affected by Unconfigured Carbon Footprint
  • Building Block Definition API Uses Platform Type References
  • Refreshed Building Block Runner Management UI
  • meshBuildingBlock API now Includes Lifecycle Information in Status
  • Disable AWS IAM Replication with the New 'None' IAM Type

Ticket Details​

Improved Runner Detail and Create Pages with a Context Header​

Audience: User

Description​

The building block runner detail and create screens now have a consistent page header, matching the style of the building block definition detail view. The header shows the runner's name and UUID for quick reference, along with a "Back to Runners" navigation link so you can easily return to the runners overview.

Improved Compatibility for Building Block Dependencies​

Audience: User

Description​

We fixed limitations when wiring building blocks together. String-compatible output types (string, code, single-select, multi-select) can now be used as the source for string or code inputs on dependent building blocks.

For manual building blocks, single-select inputs now automatically produce a string output, and multi-select inputs produce a code output. This means you can chain manual building blocks that use selection inputs into downstream building blocks without hitting type mismatch errors.

We also fixed a bug in the building block definition version API that allowed invalid output types to be set on manual building block definition versions. The API now validates that outputs match the types derived from their corresponding inputs.

Improved Reliability When Sending Updates to Deletion Runs​

Audience: User

Description​

We resolved an issue that caused errors when sending updates to building block deletion runs. Updates to deletion runs now complete reliably without unexpected errors.

Improved Runner Creation and Management in the Platform Builder​

Audience: User

Description​

We improved how you create and manage building block runners in the platform builder. When creating a new runner, a selection dialog now guides you through choosing the right runner type before filling out the form.

We also introduced a clearer distinction between meshcloud-managed runners (pre-deployed with meshStack) and self-hosted runners (created by your workspace team). meshcloud-managed runners are read-only and cannot be edited or deleted, making it easier to identify which runners you own and can configure.

Public Key Generation Guide in Building Block Runner Creation​

Audience: User

Description​

When creating a new building block runner, you now get step-by-step instructions for generating the required public key right inside the form. A "How to generate a key" button next to the Public Key field opens a modal with clear, OS-specific commands for macOS, Linux, and Windows, and automatically selects the right tab based on your operating system.

Fixed Date Selectors Being Cut Off in Tables​

Audience: User

Description​

We fixed an issue where date selector dropdowns in tables were cut off. You can now fully interact with date pickers without any visual clipping.

Metering Status No Longer Affected by Unconfigured Carbon Footprint​

Audience: User

Description​

We fixed an issue where the platform metering status could show as "Failed" due to carbon footprint data collection results, even when the BigQuery table for CO2e was not configured on the platform. meshStack now ignores the carbon footprint collection status when determining the overall metering status if carbon footprint reporting is not configured for the platform.

Building Block Definition API Uses Platform Type References​

Audience: User

Description​

The spec.supportedPlatforms field in the meshBuildingBlockDefinition API has changed from a plain list of strings to a list of meshPlatformType references.

This makes the field consistent with how other meshObject API fields reference meshStack entities, and ensures that the values are clearly typed and validated.

How to use​

Previously, you would specify supported platforms as a plain string array:

"supportedPlatforms": [ "AZURE" ]

Now each entry must be a meshPlatformType reference object with a kind and name field:

"supportedPlatforms": [ { "kind": "meshPlatformType", "name": "AZURE" } ]

The name corresponds to the metadata.name of the meshPlatformType.

Refreshed Building Block Runner Management UI​

Audience: User

Description​

We've improved the building block runner management screens to make them cleaner and easier to use. Implementation types (such as Terraform, GitHub Workflow, or GitLab Pipeline) now display with recognizable icons throughout the runner overview and detail screens.

meshBuildingBlock API now Includes Lifecycle Information in Status​

Audience: User

Description​

As part of our work to finalize the meshBuildingBlock API for GA, we moved lifecycle information for building blocks in the meshObject API from the metadata section to the status section, where it belongs according to our API conventions.

The status.lifecycle object now contains the building block's lifecycle state (e.g. ACTIVE or MARKED_FOR_DELETION), its creation date (createdOn), and, if applicable, when and by whom it was marked for deletion (markedForDeletionOn, markedForDeletionBy).

The metadata.createdOn, metadata.markedForDeletionOn, and metadata.markedForDeletionBy fields have been removed. Since the meshBuildingBlock API is a preview version, this is a breaking change. Please update your integrations accordingly.

Disable AWS IAM Replication with the New 'None' IAM Type​

Audience: User

Description​

You can now set the IAM type to 'None' when configuring an AWS platform in meshStack. In this mode, meshStack still replicates and manages AWS accounts, but skips all IAM permission and group replication in AWS IAM Identity Center.

How to use​

This is useful when you want meshStack to handle account provisioning without managing user access via IAM Identity Center, allowing you to set up access control separately without interference from meshStack's replication. It also allows you to iteratively set up an AWS platform in meshStack without worrying about IAM replication until you're ready to enable it.