Skip to main content

Release 2026.14.0

· 6 min read
meshcloud

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

This release includes the following issues:

  • Marketplace No Longer Shows a Platform Builder Banner Above Services
  • Improved Visual Design of Featured Service Cards in the Marketplace
  • Cleaner Building Block Inputs View
  • Fix Saving GitLab Building Block Definitions
  • Fix Global Group Binding to Projects via meshObject API
  • Fix Sidebar Navigation Collapse/Expand Animation
  • Optional Git Reference Support for Azure DevOps Building Block Definitions
  • Fix Content Shifting When Opening Modals
  • Fix Deploying Draft Building Blocks Without Inputs
  • Fix Stale Form Data When Creating a New Building Block Definition
  • Skip Workspace Selection When Importing a Building Block Definition
  • Redesigned Platform Builder Welcome Experience
  • Abort Building Block Runs in Pending, Waiting, or Dependency States
  • Show Missing Outputs When Building Block Fails
  • Input Validation for CODE Type Inputs in Building Block Definition Versions

Ticket Details​

Marketplace No Longer Shows a Platform Builder Banner Above Services​

Audience: User

Description​

The "Open Platform Builder" banner that used to sit above the services in the marketplace has been removed. Instead, a card now appears at the end of the service list, so you can browse services without a banner pushing everything down.

Audience: User

Description​

We've refreshed the look of featured service cards in the marketplace. They now display with a clean white background and a blue border, matching the style of regular service cards while still standing out clearly. We've also removed the service count from the "All Services" heading to keep the interface cleaner and less cluttered.

Cleaner Building Block Inputs View​

Audience: User

Description​

When you view the details of a building block, we now show you only the relevant inputs first, while static inputs (managed automatically by the platform) are hidden by default. Should you need to see the static inputs, you can always reveal them by clicking the corresponding button. This makes it easier to focus on the fields that actually matter to you.

Fix Saving GitLab Building Block Definitions​

Audience: User

Description​

We fixed a bug where updating an existing building block definition with a GitLab implementation would always fail with a "Could not read request body" error. You can now update GitLab building block definitions without errors.

Fix Global Group Binding to Projects via meshObject API​

Audience: User

Description​

We fixed a bug where assigning a global group to a project via the meshObject API always failed with a "group does not exist" error, even though the group existed. You can now successfully assign global groups to projects using the meshObject API.

Fix Sidebar Navigation Collapse/Expand Animation​

Audience: User

Description​

We fixed a visual glitch in the sidebar navigation where collapsing or expanding a section caused a small jump at the end of the animation. The sidebar now collapses and expands smoothly.

Optional Git Reference Support for Azure DevOps Building Block Definitions​

Audience: User

Description​

You can now specify an optional Git reference (e.g. a branch or tag like refs/heads/my-branch) when configuring an Azure DevOps pipeline building block definition. This allows you to pin a building block to a specific branch or tag of your pipeline's repository.

When no Git reference is provided, Azure DevOps uses its default branch as before.

Fix Content Shifting When Opening Modals​

Audience: User

Description​

We fixed a small visual bug where the page content would shift a bit when opening a modal dialog.

Fix Deploying Draft Building Blocks Without Inputs​

Audience: User

Description​

We fixed a bug where the "Deploy building block" button never became active when deploying a draft building block for testing that has no user-configurable inputs (all inputs are set statically by the definition).

Fix Stale Form Data When Creating a New Building Block Definition​

Audience: User

Description​

We fixed a bug where the "General Information" form in the building block definition creation wizard was pre-filled with data from a previously created building block definition.

Skip Workspace Selection When Importing a Building Block Definition​

Audience: User

Description​

When you import a building block definition from the meshStack Hub and you only have access to a single workspace, we now skip the workspace selection step and navigate you directly to the new definition form. This saves you an unnecessary click and makes the import flow faster.

Redesigned Platform Builder Welcome Experience​

Audience: User

Description​

We redesigned the welcome section of the platform builder dashboard to guide you through the initial setup of your platform with a clear, step-by-step onboarding flow. The new experience walks you through creating your first Building Block Definition and integrating your first platform, with quick-start examples for AWS, Azure, and GCP.

How to use​

When you open the platform builder dashboard as a new user, you will see the updated welcome section with guided steps. Each step includes cards that link directly to relevant resources like the meshStack Hub for Building Block examples, or pre-filled platform integration wizards for supported cloud providers.

Abort Building Block Runs in Pending, Waiting, or Dependency States​

Audience: User

Description​

You can now abort building block runs that are pending (queued but not yet started), waiting for input, or waiting for a dependent building block to complete. This gives you full control to abort stuck or unwanted runs, regardless of their current state.

Show Missing Outputs When Building Block Fails​

Audience: User

Description​

When a building block fails because it did not emit all outputs defined in the building block definition, you now see a clear failure reason and which specific outputs are missing. Previously, the building block was just marked as failed without any details, making it hard to understand what went wrong.

Input Validation for CODE Type Inputs in Building Block Definition Versions​

Audience: User

Description​

When creating or updating a building block definition version via the API, we now validate that inputs of type CODE have their argument provided as a JSON-escaped string. If you pass a raw JSON object instead of an escaped string, the API returns a clear error message explaining what went wrong. Please refer to our API documentation for details on the correct format.