Skip to main content

Release 2026.33.0

· 4 min read
meshcloud

Release period: 2026-08-10 to 2026-08-12

This release includes the following issues:

  • Fix Owning Workspace Text Styling on Building Block Definition Page
  • Building Blocks Using the Author Input No Longer Run Without a Reason
  • Fixed Duplicate Checkout Permission Entries for API Keys
  • Parent Building Blocks Are Now Referenced by meshObject Ref
  • Reliable Loading Feedback When Deleting a Workspace
  • Badge Colors Tuned for Accessibility
  • Platform Contributors Can Now See the Tenants of Their Landing Zones

Ticket Details​

Fix Owning Workspace Text Styling on Building Block Definition Page​

Audience: User

Description​

We fixed the styling of the owning workspace text on the building block definition page. It now matches the definition and version identifiers shown right below it, so the three lines read as one consistent group instead of standing out with a different size.

Building Blocks Using the Author Input No Longer Run Without a Reason​

Audience: User

Description​

Building Blocks that use the Author input could start a run even though none of their input values had changed. On Workspaces with many such Building Blocks, these runs could fill the run pipeline and delay other Building Block work. meshStack now starts a run only when an input value really changed.

Fixed Duplicate Checkout Permission Entries for API Keys​

Audience: User

Description​

When creating or editing an API key, the "Building Block Runs" permission group used to show the "Checkout" permission three times instead of the three distinct permissions it actually controls: Checkout, Download, and Upload. Because of this, you could not grant the Download or Upload permission through the panel at all. We fixed the permission list so each permission now appears once, with its own label and description, and all three can be granted independently.

Parent Building Blocks Are Now Referenced by meshObject Ref​

Audience: User

Description​

The meshBuildingBlock v2-preview meshObject API has a new spec.parentBuildingBlockRefs field. Each entry is a meshObject reference that names the parent with kind and uuid, the same shape this API already uses for spec.targetRef and spec.buildingBlockDefinitionVersionRef.

spec.parentBuildingBlocks is deprecated. It is still accepted and still returned, so every released Terraform provider keeps working unchanged. Send either field; if you send both, they must name the same parent Building Blocks, otherwise you get a 400. Responses carry both fields with the same content.

Inside the deprecated field, definitionUuid is now always derived from the referenced Building Block, on an upgrade as well. meshStack ignores the value you send and returns the derived one.

The deprecated field will be removed when this API graduates from preview to GA.

Reliable Loading Feedback When Deleting a Workspace​

Audience: User

Description​

When you delete your workspace, the confirmation button now stays disabled and shows a loading indicator for the entire deletion process, not just its first step. Previously, the button could look idle for a few seconds before you were redirected, making it unclear whether anything was happening.

Badge Colors Tuned for Accessibility​

Audience: User

Description​

We made colors of the badges more accessible for users with vision impairments.

Platform Contributors Can Now See the Tenants of Their Landing Zones​

Audience: User

Description​

If your workspace contributes to a platform owned by another workspace, the Tenants tab of that platform failed with "You are not allowed to use this Landing Zone." even when you owned landing zones on it. You now see the tenants running on the landing zones your workspace owns there. If you do not own a landing zone on that platform yet, the tab now opens with an empty list instead of an error.