|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.29.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-07-09 to 2025-07-16 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Improved URL validation for GitHub and GitLab integrations |
| 10 | +* Fix Saving of Building Block Sensitive File Inputs |
| 11 | +* Fixed Chargeback Message for Excluded TURPs |
| 12 | +* Communications Badge Count Not Updating |
| 13 | +* Search and filter workspace resources |
| 14 | +* Enhanced Building Block with Summary support |
| 15 | +* Building Block runners use external endpoints for callbacks |
| 16 | +* Overview for all resources in workspace |
| 17 | +* User Permissions source for Workspace Building Blocks |
| 18 | +* Fix Communication Due Date |
| 19 | +* Extend Communication Status Filter |
| 20 | +* Fixed Adding Users During Workspace Creation |
| 21 | +* Resource links on building block cards |
| 22 | +<!--truncate--> |
| 23 | + |
| 24 | +## Ticket Details |
| 25 | +### Improved URL validation for GitHub and GitLab integrations |
| 26 | +**Audience:** User<br> |
| 27 | + |
| 28 | +#### Description |
| 29 | +Integrations with GitHub and GitLab now sanitize and validate the provided URLs. This prevents issues with trailing slashes and whitespace ensuring more robust integration experience. |
| 30 | + |
| 31 | +### Fix Saving of Building Block Sensitive File Inputs |
| 32 | +**Audience:** User<br> |
| 33 | + |
| 34 | +#### Description |
| 35 | +A bug that was present since the v2025.28.0 release prevented the proper saving or updating of the sensitive |
| 36 | +building block static file inputs. |
| 37 | +They were incorrectly saved unencrypted and the building blocks did not run successfully. Please re-upload those |
| 38 | +files and/or rotate the secrets associated with them. |
| 39 | + |
| 40 | +### Fixed Chargeback Message for Excluded TURPs |
| 41 | +**Audience:** User<br> |
| 42 | + |
| 43 | +#### Description |
| 44 | +Previously, users would see a misleading message stating that "No tenant usage reports were recorded," which |
| 45 | +did not reflect the actual presence of non-finalized TURPs. In this release, the user interface now displays a |
| 46 | +clearer message in such cases, informing users that TURPs exist but were not finalized at the time of statement |
| 47 | +finalization. |
| 48 | + |
| 49 | +### Communications Badge Count Not Updating |
| 50 | +**Audience:** User<br> |
| 51 | + |
| 52 | +#### Description |
| 53 | +This fixes a cosmetic bug that caused no immediate update of the |
| 54 | +badge count after the user acknowledged a communication. |
| 55 | + |
| 56 | +### Search and filter workspace resources |
| 57 | +**Audience:** User<br> |
| 58 | + |
| 59 | +#### Description |
| 60 | +We enhanced the workspace resource overview with search and filtering capabilities. You can now quickly find |
| 61 | +specific resources by searching for their names and filter resources by type (Projects, Tenants, or Building Blocks) |
| 62 | +to focus on what you need. |
| 63 | + |
| 64 | +#### How to use |
| 65 | +Navigate to your workspace overview page where you'll see a search bar at the top of the resource grid. Enter any part |
| 66 | +of a resource name to search, or use the filter buttons on the right to show only specific resource types. You can |
| 67 | +combine search and filtering to narrow down results even further. The search works with partial matches and is |
| 68 | +case-insensitive for your convenience. |
| 69 | + |
| 70 | +### Enhanced Building Block with Summary support |
| 71 | +**Audience:** User<br> |
| 72 | + |
| 73 | +#### Description |
| 74 | +Building blocks now support a new "Summary" output type that displays markdown content directly in the building block |
| 75 | +details view. We've also streamlined the building block creation process to redirect directly to the newly created |
| 76 | +building block details page instead of the list view. |
| 77 | + |
| 78 | +#### How to use |
| 79 | +When creating building block definitions, you can now add outputs with the assignment type "Summary" to provide |
| 80 | +guidance and next steps to users. |
| 81 | + |
| 82 | +### Building Block runners use external endpoints for callbacks |
| 83 | +**Audience:** User<br> |
| 84 | + |
| 85 | +#### Description |
| 86 | +We fixed an issue where Building Block runners were using internal endpoints, which caused problems when integrating with |
| 87 | +external systems that require callback URLs. This affected GitHub Actions, GitLab CI/CD pipelines, and asynchronous |
| 88 | +Terraform runs that needed to communicate back to meshStack. |
| 89 | + |
| 90 | +### Overview for all resources in workspace |
| 91 | +**Audience:** User, Customer<br> |
| 92 | + |
| 93 | +#### Description |
| 94 | +A new grid view displays all workspace resources (projects, tenants, building blocks) in a |
| 95 | +unified overview with visual relationship indicators within the workspace overview tab. |
| 96 | +Users can quickly identify connections between resources and navigate directly to related |
| 97 | +resources through clickable relationship badges. |
| 98 | + |
| 99 | +#### How to use |
| 100 | +Navigate to the workspace overview page to see the new grid layout showing all your workspace |
| 101 | +resources. Each resource card displays its type, name, and relationships to other resources. |
| 102 | +Click on relationship badges to navigate to connected resources. |
| 103 | + |
| 104 | +### User Permissions source for Workspace Building Blocks |
| 105 | +**Audience:** User<br> |
| 106 | + |
| 107 | +#### Description |
| 108 | +We now support the "User Permissions" source for workspace-level building blocks. This provides all workspace users |
| 109 | +with their workspace roles as input data for your building block. |
| 110 | + |
| 111 | +#### How to use |
| 112 | +When configuring inputs for workspace-level building blocks, you can now select "User Permissions" as a source. This is |
| 113 | +particularly useful for building blocks that need to set up user access or permissions based on the workspace's user |
| 114 | +assignments. The user permissions data includes user details like username, email, and roles, making it easy to |
| 115 | +configure access controls or user-specific resources in your building blocks. |
| 116 | + |
| 117 | +### Fix Communication Due Date |
| 118 | +**Audience:** Partner<br> |
| 119 | + |
| 120 | +#### Description |
| 121 | +Previously, it was possible to change the due date of communications of type |
| 122 | +Notification, although this was not intended. This has been fixed, such that due |
| 123 | +dates can now only be specified and changed for Communications of type |
| 124 | +'Action Required'. |
| 125 | + |
| 126 | +### Extend Communication Status Filter |
| 127 | +**Audience:** Customer<br> |
| 128 | + |
| 129 | +#### Description |
| 130 | +Previously, when viewing the received communications within the workspace |
| 131 | +area, filtering communications by the status 'Received' was not possible. |
| 132 | +This has been fixed. |
| 133 | + |
| 134 | +### Fixed Adding Users During Workspace Creation |
| 135 | +**Audience:** User<br> |
| 136 | + |
| 137 | +#### Description |
| 138 | +This fix addresses the issue where users could not be added during workspace creation. |
| 139 | + |
| 140 | +### Resource links on building block cards |
| 141 | +**Audience:** User<br> |
| 142 | + |
| 143 | +#### Description |
| 144 | +Building blocks now support Resource URL outputs that display as clickable links directly on the building block card. |
| 145 | +This makes it easier to access external resources and services provided by your building blocks. |
| 146 | + |
| 147 | +#### How to use |
| 148 | +When defining building block outputs, you can now select "Resource URL" as the output type. These outputs will appear |
| 149 | +as clickable links on the building block card with an external link icon. The display name you configure for the |
| 150 | +output will be used as the link text. You can define multiple Resource URL outputs for a single building block to |
| 151 | +provide access to different resources or dashboards related to your infrastructure. |
| 152 | + |
0 commit comments