Skip to main content

Release 2026.21.0

· 4 min read
meshcloud

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

This release includes the following issues:

  • Deleted Building Blocks No Longer Appear in Workspace Resources
  • Return Soft-Deleted Building Blocks via meshObject API
  • meshObject API: Manual Building Blocks Only Support PURGE Deletion Mode
  • Auto-detect Runner Connection After Docker Setup
  • View Docker Instructions for a Runner in meshPanel
  • Prevent Duplicate API Key Actions Within Right Groups
  • Building Block Runners Now Accept RSA Public Keys
  • Freely Edit Inputs and Outputs of Draft Building Block Definition Versions

Ticket Details​

Deleted Building Blocks No Longer Appear in Workspace Resources​

Audience: User

Description​

We fixed a bug where building blocks that were deleted or marked for deletion still appeared in the workspace resources view. You will now only see active building blocks there.

Return Soft-Deleted Building Blocks via meshObject API​

Audience: User

Description​

The meshObject API now supports filtering building blocks by lifecycle state, allowing you to also retrieve soft-deleted building blocks via the API.

By default, only active (non-deleted) building blocks are returned, preserving backward compatibility. Please refer to our public API documentation for details on how to use this filter.

Important: To ensure building block deletion works correctly, you must upgrade the Terraform provider to version 0.20.9 or later. Building block deletion will not succeed with older provider versions.

meshObject API: Manual Building Blocks Only Support PURGE Deletion Mode​

Audience: User

Description​

We now correctly enforce that building block definition versions using the manual implementation type can only use PURGE as their deletion mode. Manual building blocks have no deletion automation, so DELETE - which implies running automated cleanup - is not a valid option for them.

If you use the meshBuildingBlockDefinitionVersion API to create or update a manual building block definition version, make sure to set deletionMode to PURGE. Requests that specify DELETE will now be rejected with a validation error.

Auto-detect Runner Connection After Docker Setup​

Audience: User

Description​

After creating a new building block runner, meshPanel now takes you directly to the runner's setup page. There you find a ready-to-use Docker configuration and a docker run command tailored to your runner. Once the container is running, meshPanel automatically detects when the runner connects and shows you a confirmation - so you know everything is working without having to check manually.

View Docker Instructions for a Runner in meshPanel​

Audience: User

Description​

When you open a runner's detail page, you can now find a ready-to-use Docker setup guide directly on the page. The guide provides a pre-filled configuration file and a complete docker run command tailored to your runner, so you can get a self-hosted runner up and running without leaving meshPanel.

Prevent Duplicate API Key Actions Within Right Groups​

Audience: User

Description​

We now prevent API key permission groups from containing the same action more than once for the same scope. This keeps permission lists unambiguous and fixes the Building Block Runs group.

How to use​

No action is needed. API key permissions now show distinct actions within a group, so you can select the intended permission without duplicate entries.

Building Block Runners Now Accept RSA Public Keys​

Audience: User

Description​

You can now provide a plain RSA public key (PEM-encoded, BEGIN PUBLIC KEY format) when creating or updating a building block runner, in addition to the previously required X.509 certificate. This simplifies the key generation process - you no longer need to create a self-signed certificate and can use a standard RSA key pair instead. Existing runners using X.509 certificates continue to work without any changes.

How to use​

The updated help dialog in meshPanel now guides you through generating a simple RSA key pair and explains the commands step by step.

Freely Edit Inputs and Outputs of Draft Building Block Definition Versions​

Audience: User

Description​

You can now freely edit the inputs and outputs of a building block definition version while it is in draft state, even if building block instances using that version already exist. Previously, any existing instance would block all input and output changes, forcing platform engineers to delete instances or work around the restriction. Note that removing an input will also remove it from all existing building blocks using that draft version once you save. Changing an output that another definition depends on as an input may break building block execution for the affected workspace - you will need to manually fix that dependency connection.