Added release notes and version entries for 2025.54.0

Author: GitHub Actions

blog/2025-12-16-Release-0.md

@@ -0,0 +1,117 @@
+---
+author: meshcloud
+title: Release 2025.54.0
+---
+
+Release period: 2025-12-10 to 2025-12-16
+
+This release includes the following issues:
+* Improved Workspace Search in Tables
+* Configurable Enforcement of Azure Subscription Name Pattern
+* Improved User Display in Access Control Tables
+* Increased Size Limit for Building Block Inputs and Outputs
+* Removed Active Payment Methods Limit per Workspace
+* Fix Workspace Selection Limit in Communication Center
+* Large Input support for Building Blocks using GitHub Actions
+* Retrieve Individual Building Block Runs via meshObject API
+<!--truncate-->
+
+## Ticket Details
+### Improved Workspace Search in Tables
+**Audience:** User<br>
+
+#### Description
+When searching for workspaces in various tables throughout meshStack, you can now search with any part of a 
+workspace identifier. Previously, the search only showed results that started with your search term, which made it 
+difficult to find specific workspaces when the search term appeared later in the identifier. Now you can type any 
+part of a workspace identifier to see all partial matches, or select a workspace from the dropdown for an exact 
+match.
+
+#### How to use
+When using workspace search filters in tables, start typing any part of a workspace identifier, and the list will 
+automatically show all matching workspaces. You can either select a workspace from the dropdown for an exact match, 
+or continue typing to filter based on your search term.
+
+### Configurable Enforcement of Azure Subscription Name Pattern
+**Audience:** User<br>
+
+#### Description
+You can now control whether meshStack updates Azure subscription display names to match your configured naming pattern.
+Previously, meshStack only assigned subscription names during initial provisioning.
+To use this feature enable the "Update Subscription Name" option in an Azure platform configuration and
+assign the `Microsoft.Subscription/rename/action` permission to the meshStack service principal.
+
+#### How to use
+When enabled, meshStack ensures subscription names always match your configured naming pattern.
+When disabled, meshStack only sets subscription names during creation and leaves them unchanged during subsequent replications.
+This allows you to enforce strict naming conventions or allow external modifications to subscription names.
+Note: The capability to update subscription names was originally introduced in meshStack v2025.53 and was enabled by default.
+Unfortunately, this could result in replication failures when meshStack's service principal's were not given the required
+`Microsoft.Subscription/rename/action` permission in Azure. This release therefore introduces an explicit
+configuration option so that platform teams can control the rollout of this new capability to their meshStack.
+
+### Improved User Display in Access Control Tables
+**Audience:** User<br>
+
+#### Description
+User information in access control tables is now displayed with the user's full name
+on the first line and their email address on a separate line below. This makes it
+easier to identify users at a glance and improves readability, especially when
+managing access for multiple team members.
+
+Note: This change only affects customers who have access to the new access control v2 feature. If you are using the 
+standard access control interface, this change does not apply to you.
+
+### Increased Size Limit for Building Block Inputs and Outputs
+**Audience:** User<br>
+
+#### Description
+We increased the maximum size limit for building block inputs and outputs from 64 KB to 16 MB. This allows you to 
+work with larger data volumes in your building block definitions, runs, and configurations without hitting size 
+constraints.
+
+### Removed Active Payment Methods Limit per Workspace
+**Audience:** User<br>
+
+#### Description
+Previously, workspaces were limited to 350 active payment methods. This limit has been completely removed, allowing
+you to create and manage an unlimited number of payment methods per workspace.
+
+### Fix Workspace Selection Limit in Communication Center
+**Audience:** User<br>
+
+#### Description
+We fixed a bug in the communication center that prevented sending communications to more than 100 workspaces. Previously,
+when targeting workspaces for a communication, only the first 100 workspaces were loaded and available for selection.
+This made it impossible to send communications to additional workspaces beyond this limit. Now, all workspaces are
+loaded correctly, allowing you to send communications to any number of workspaces in your organization.
+
+### Large Input support for Building Blocks using GitHub Actions
+**Audience:** User<br>
+
+#### Description
+Building blocks with many inputs or large user-provided values can now be configured to avoid GitHub's 
+workflow input size limits. A new "Pass only API URL" option allows workflows to receive only the API 
+URL instead of the full building block data, preventing failures when the total input size exceeds 
+GitHub's limits (65,535 characters for GitHub Cloud, potentially lower for GitHub Enterprise).
+
+#### How to use
+In the building block definition, navigate to the GitHub workflow implementation settings and enable the 
+"Pass only API URL (recommended for large payloads)" option. When enabled, your GitHub workflow will 
+receive only the `buildingBlockRunUrl` input. You'll need to update your workflow to fetch the building 
+block data from this URL using the meshStack API. When disabled (default), the workflow continues to 
+receive the old `buildingBlockRun` (base64-encoded JSON) inputs for backward compatibility.
+See https://github.com/meshcloud/actions-register-source/releases/tag/v2.0.0 for upgrade instructions.
+
+### Retrieve Individual Building Block Runs via meshObject API
+**Audience:** User<br>
+
+#### Description
+The meshObject API now supports retrieving individual building block runs by their UUID. 
+This allows platform engineers to access detailed status information about a specific building block run, including inputs,
+outputs, and error details if applicable.
+
+#### How to use
+Platform teams can add a new permission to their API keys to allow access to this endpoint
+for building block runs using building block definitions or runners that they own.
+