Skip to main content

Release vNext

· 6 min read
meshcloud

Release period: 2026-02-25 to 2026-03-04

This release includes the following issues:

  • Fix Internal Error When Removing a User from a Workspace
  • Reverted GitHub Actions Run Tracking Improvement
  • Annual Pricing Option for Building Block Definitions
  • Fix for Building Block Notifications Not Firing on Run Status Changes
  • Fix Azure Subscription Owner Object ID Handling in meshObject API and Panel
  • Terraform Building Block Runner Now Respects Custom Variable Definitions
  • Removal of the Cloud Universe Feature
  • Aborting a Building Block Run Now Returns Correct Response to Runners
  • Validation Added for Building Block Definition Symbol Field
  • Fix Group Cleanup After Tenant Move on GCP, OpenStack, AWS and Azure
  • Improved Reliability of Building Block Runs Job Retries
  • Marketplace Service Instance Relation Changes
  • Optimized Building Block Triggering and Event Attribution

Ticket Details​

Fix Internal Error When Removing a User from a Workspace​

Audience: User

Description​

We fixed a bug where removing a user from a workspace could result in an internal error in certain edge cases.

Reverted GitHub Actions Run Tracking Improvement​

Audience: User

Description​

We reverted the recently introduced improvement for tracking GitHub Actions building block runs. The new GitHub API for returning the run ID directly on dispatch is not yet available on private GitHub installations, which caused issues for affected customers. meshStack now uses the previous polling-based approach again to ensure compatibility with all GitHub installations. We will reintroduce the improvement once the new API is available and applied for private GitHub installations as well.

Annual Pricing Option for Building Block Definitions​

Audience: User

Description​

You can now configure an annual price for building blocks in addition to the existing daily and monthly options. An annual fee is charged once per year on the anniversary of the building block's creation date. All other monthly billing periods receive no charge, making it ideal for resources with yearly license costs or annual commitments (e.g. AI platform subscriptions or cloud-provider annual agreements).

How to use​

To configure an annual price, go to the building block definition in the platform builder, open the General tab, and select Annually from the recurring fee dropdown. Please note that pricing is only supported on tenant-level building blocks, as all usage-reporting is based on projects and chargeback uses the project's associated payment method.

Fix for Building Block Notifications Not Firing on Run Status Changes​

Audience: User

Description​

We fixed a bug where building block notifications for failed or succeeded runs were not sent when a runner reported the final run status via the meshObject API. This affected platform operators and building block definition owners who rely on notifications to be alerted when a building block run fails or succeeds.

Fix Azure Subscription Owner Object ID Handling in meshObject API and Panel​

Audience: User

Description​

We fixed two issues with the Azure Subscription Owner Object ID configuration. First, the meshObject API now correctly accepts null for the subscriptionOwnerObjectIds field. Previously, sending null resulted in a 400 error even though the API documentation marked the field as optional. Both null and an empty list are now treated as "no subscription owner configured". Second, the panel now correctly persists the "Do not require a Subscription Owner" override setting. Previously, this setting could be lost after saving and reloading the platform configuration because it was derived from the subscription owner list being empty, which was ambiguous.

Terraform Building Block Runner Now Respects Custom Variable Definitions​

Audience: User

Description​

We improved how the Terraform building block runner handles the meshStack-provided variables (e.g. meshstack_building_block_run_b64, meshstack_building_block_id). If you have already defined variable blocks for these in your Terraform configuration, we no longer overwrite them.

In addition, the .auto.tfvars file written by meshStack is now assigned the lowest alphabetical precedence. Any .auto.tfvars files in your repository load after it and can override the meshStack-provided values, following standard Terraform variable precedence rules.

Removal of the Cloud Universe Feature​

Audience: User

Description​

We have removed the Cloud Universe feature from meshStack. The Cloud Universe was a read-only graph visualization of meshStack entities (users, groups, workspaces, projects, and tenants) accessible via the admin "Cloud Foundation" tab. It has been removed as part of our ongoing effort to streamline the product and focus on features that provide the most value to our users.

Aborting a Building Block Run Now Returns Correct Response to Runners​

Audience: User

Description​

We fixed a bug where aborting a building block run could cause runners to receive an unexpected HTTP 500 error instead of the correct response indicating the run was aborted. If you are using custom runners or have built automated pipelines that integrate via the building block run API, this fix ensures your runners now reliably receive the correct runAborted: true response and can handle the abort gracefully.

Validation Added for Building Block Definition Symbol Field​

Audience: User

Description​

The spec.symbol field on building block definitions now validates that the value is a safe image URI. Valid values are inline image data URIs using PNG, JPEG, GIF, or WebP formats (e.g., data:image/png;base64,...) or an http(s):// URL pointing to an image. SVG data URIs and other non-image data URIs are no longer accepted, as they could pose a cross-site scripting (XSS) risk. If you use Terraform or another API client to manage building block definitions with a custom symbol, please ensure your symbol value uses one of the supported formats above.

Fix Group Cleanup After Tenant Move on GCP, OpenStack, AWS and Azure​

Audience: User

Description​

When a tenant was moved to a different workspace, the old platform groups (tied to the previous workspace) could get stuck and never be cleaned up on GCP, OpenStack, AWS and Azure. This happened when the platform was temporarily slow to respond during replication and required manual cleanup. We fixed this so that meshStack now always preserves the old group metadata across failed replication attempts, ensuring the cleanup of stale groups is retried successfully on the next replication cycle.

Improved Reliability of Building Block Runs Job Retries​

Audience: User

Description​

We fixed a bug where building block runs could get stuck or fail unexpectedly when jobs failed to execute (e.g. due to node pressure or resource constraints). In those cases, the retried job would report an incorrect status back to meshStack. The run would then appear failed or stuck without a clear reason.

Marketplace Service Instance Relation Changes​

Audience: User

Description​

We improved the internal architecture of marketplace service instances to better support multiple marketplaces per location. As part of this change, we removed the deprecated tenant-aware service support from the user interface. This change resolves issues that previously occurred when configuring multiple Open Service Broker (OSB) marketplaces within the same location.

Optimized Building Block Triggering and Event Attribution​

Audience: User

Description​

We optimized how building blocks are triggered for execution. Building blocks are now grouped by workspace before triggering, which reduces unnecessary processing and improves overall performance when updating multiple building blocks. Additionally, we improved the event attribution in the building block audit trail.