Skip to main content

Release 2026.1.0

· 5 min read
meshcloud

Release period: 2025-12-17 to 2026-01-07

This release includes the following issues:

  • Fix Dependent Mandatory Building Block Selection in Project Creation
  • Improved Error Message for Wrong Azure Subscription Enrollment Selection
  • Improved Building Block Execution with Isolated Run Jobs
  • Improved Filtering for meshPlatform and meshLandingZone APIs
  • Fix Event Log Filtering Error in Workspace View
  • Related Service Description Shown in Marketplace
  • Fix Workspace and Project Links in Platform Builder for Non-Admins
  • Fix Removing Expiration Date From Users and Groups
  • Add Feature Preview Rollout Dates

Ticket Details​

Fix Dependent Mandatory Building Block Selection in Project Creation​

Audience: User

Description​

When creating a project with a tenant that requires a Landing Zone, if the Landing Zone contains a mandatory Building Block that itself depends on another Building Block, the dropdown for the dependent Building Block was empty and displayed "create building block first!" This has been fixed.

Improved Error Message for Wrong Azure Subscription Enrollment Selection​

Audience: User

Description​

When creating an Azure subscription with an incorrect enrollment type selected (e.g., using a Legacy Enterprise Agreement configuration when a Microsoft Customer Agreement is required), meshStack now provides a clear and actionable error message. Previously, such misconfigurations resulted in generic error messages that made troubleshooting difficult.

Improved Building Block Execution with Isolated Run Jobs​

Audience: User

Description​

We have improved building block execution by enabling isolated and ephemeral run jobs. This enhancement provides better security through more fine-granular Workload Identity Federation (WIF) tokens and improves parallel building block execution performance. Please note that this is a breaking change for environments already using WIF-based building blocks, and we will coordinate the rollout individually with affected customers.

How to use​

This improvement is currently rolled out to QA and Trial environments that do not yet use WIF-based building blocks. Building blocks now execute in isolated environments, ensuring better resource isolation and security. If you use building blocks with cloud platform authentication via Workload Identity Federation, you will benefit from more fine-granular access tokens that are scoped to a building block definition. Additionally, parallel execution of multiple building blocks is now more efficient. For environments already using WIF-based building blocks, we will work with you directly to schedule the migration.

Improved Filtering for meshPlatform and meshLandingZone APIs​

Audience: User

Description​

The meshPlatform and meshLandingZone APIs now support explicit query parameters for filtering. You can filter platforms by name, location, owner, publication state, restriction, display name, and contributing workspaces. Landing zones can be filtered by name, display name, platform, disabled state, restriction and owner. Please note that the generic searchTerm parameter on the meshPlatform v2 API has been removed - if you previously filtered by ownedByWorkspace using searchTerm, you must now use the dedicated ownedByWorkspace query parameter instead.

Fix Event Log Filtering Error in Workspace View​

Audience: User

Description​

Fixed an error that occurred when filtering event logs by event type within a workspace. The event log filtering now works correctly and displays the filtered results as expected.

Audience: User

Description​

Previously, when viewing the marketplace within a workspace, the description for a related service was not displayed. This issue has been fixed, and the description is now properly shown alongside related services in the marketplace.

Audience: User

Description​

Users in the platform builder area previously saw clickable links to workspace and project admin pages in the inventory tenants view, even though they couldn't access those pages. Now, non-admin users in the platform builder area see workspace and project identifiers as plain text instead of broken links.

Fix Removing Expiration Date From Users and Groups​

Audience: User

Description​

Previously, removing the expiration date from a user or group assignment resulted in an error message stating that the expiration date must not be in the past. This prevented you from removing expiration dates. This issue has been fixed, and you can now successfully remove expiration dates from user and group assignments.

How to use​

When editing a user or group assignment, you can now clear the expiration date field to remove the expiration date. For workspace roles, please note that if you have configured a maximum access period in the Role Recertification section in the Admin Area, the expiration date becomes mandatory. In such cases, you will receive a validation error if you attempt to remove the expiration date.

Add Feature Preview Rollout Dates​

Audience: User

Description​

Feature Previews may now include rollout completion dates. After this date, the feature will be considered fully released and no longer in preview status. This means that users can no longer switch back to the previous version of the feature, and admins can also no longer opt out of the feature preview. The rollout completion date will be displayed in the Feature Previews area of the panel. We also added a new section for completed feature previews to help users keep track of which features have fully rolled out. For the existing feature previews of "New Marketplace Experience" and "Workspace Overview - Default View", we have set the rollout completion date to April 1st, 2026.