Skip to main content

Release 2026.3.0

· 4 min read
meshcloud

Release period: 2026-01-16 to 2026-01-21

This release includes the following issues:

  • Fixed Timeout Building Block Runs Not Being Retryable
  • Fixed Building Block Run Counting
  • Restructured meshPlatformType Lifecycle in preview API
  • Onboarding Tour in Marketplace Catalog Temporarily Disabled
  • Fixed Save Button for Code Input Default Values in Building Blocks
  • Improved Role Descriptions for Organization Admin and User
  • Custom Platforms in meshPlatform and meshLandingZone API
  • Platform Type Changes Are Now Rejected in meshPlatform and meshLandingZone API
  • Project Assignment Modal When Adding Workspace Users in Access Control V2

Ticket Details​

Fixed Timeout Building Block Runs Not Being Retryable​

Audience: User

Description​

We fixed an issue where Terraform building block runs that timed out could not be properly retried automatically and appeared stuck.

How to use​

This causes a slight change in behavior so that terminated runs cannot be updated anymore with e.g. input updates. Please make sure your external pipelines are compatible with this behavior and won't send late updates after a run was marked as successful, failed, or timed out to prevent any problems.

Fixed Building Block Run Counting​

Audience: User

Description​

We improved the way runs are counted and fixed a bug which could lead to irregular run numbers.

Restructured meshPlatformType Lifecycle in preview API​

Audience: User

Description​

We restructured the lifecycle representation in the meshPlatformType API response to use a standardized format. The lifecycle state is now returned under status.lifecycle.state instead of the previous flat status.lifecycleState field.

Additionally, we renamed the lifecycleStatus query parameter to lifecycleState when listing meshPlatformTypes via the API. This change aligns the filter parameter name with the response field, making the API more consistent and intuitive to use.

The lifecycle state values remain unchanged (ACTIVE, DEACTIVATED).

Onboarding Tour in Marketplace Catalog Temporarily Disabled​

Audience: User

Description​

The interactive onboarding tour in the marketplace catalog has been temporarily disabled due to a license change in the underlying library. We are evaluating alternative solutions and will re-enable an onboarding tour experience in a future update.

Fixed Save Button for Code Input Default Values in Building Blocks​

Audience: User

Description​

We fixed an issue where editing the default value of a code input in a building block definition did not enable the save button. Previously, you had to modify another field to trigger the save button, even though your code changes would be persisted. The save button now correctly enables when you edit code input default values.

Improved Role Descriptions for Organization Admin and User​

Audience: User

Description​

We improved the role descriptions for the "Organization Admin" and "Organization User" roles to provide clearer information about their capabilities.

Custom Platforms in meshPlatform and meshLandingZone API​

Audience: User

Description​

The meshPlatform and meshLandingZone APIs now support custom platforms via API v2-preview. You can now create and manage platforms and landing zones for your custom platform types programmatically, just like you would for built-in platform types (AWS, Azure, GCP, etc.). This enables full API-based automation workflows for proprietary or emerging cloud platforms that you've added to meshStack.

Platform Type Changes Are Now Rejected in meshPlatform and meshLandingZone API​

Audience: User

Description​

When updating a meshPlatform or meshLandingZone via the meshObject API, attempts to change the platform type are now properly rejected with a clear error message. This applies to all platform types, including both built-in platforms (AWS, Azure, GCP, etc.) and custom platforms. Previously, such changes were silently ignored, potentially causing confusion.

Project Assignment Modal When Adding Workspace Users in Access Control V2​

Audience: User

Description​

When adding new users or groups to a workspace in Access Control V2 workspace control plane, a modal now automatically appears to optionally add them to existing projects in that workspace. This streamlines the workflow of granting both workspace and project access in a single operation, matching the behavior available in Access Control V1.

Note: This change only affects customers who have access to the new access control v2 feature. If you are using the standard access control interface, this change does not apply to you.