|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.27.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-06-25 to 2025-07-03 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Migrated GitHub Integrations |
| 10 | +* List of integrations |
| 11 | +* Fix API Key Sorting by Creation Date |
| 12 | +* Fix euid filter for meshUser endpoint |
| 13 | +* Tag Catalog Support for Users and Groups |
| 14 | +* Enforce User/Group Policies during Project Creation |
| 15 | +* Improved User Authorization for Creation Flows |
| 16 | +* Admin Area Button Stays White When Focused On |
| 17 | +* Add Location Name In Platform Filter |
| 18 | +* Deprecated Platform Notification Subscriptions |
| 19 | +* Deprecated Legacy Platform Notifications |
| 20 | +* Deprecated Legacy Workspace Messages |
| 21 | +* Accessible Label For Main Navigation Bar |
| 22 | +<!--truncate--> |
| 23 | + |
| 24 | +## Ticket Details |
| 25 | +### Migrated GitHub Integrations |
| 26 | +**Audience:** Partner<br> |
| 27 | + |
| 28 | +#### Description |
| 29 | +The GitHub Actions integration used to be managed via Platforms. |
| 30 | +This has now been migrated to the new Integrations feature which is |
| 31 | +more isolated to and easier to manage. This also has the added benefit |
| 32 | +that you can directly create the integration when you create |
| 33 | +a new building block definition. |
| 34 | + |
| 35 | +### List of integrations |
| 36 | +**Audience:** Partner<br> |
| 37 | + |
| 38 | +#### Description |
| 39 | +The recently introduced GitLab integration and also the migrated GitHub integrations |
| 40 | +are now visible in one list in the Admin Area & Platform Builder. In an upcoming release |
| 41 | +we will also add the ability to create and edit integrations on this screen. |
| 42 | + |
| 43 | +### Fix API Key Sorting by Creation Date |
| 44 | +**Audience:** Customer, Partner<br> |
| 45 | + |
| 46 | +#### Description |
| 47 | +Previously, the panel returned an error when sorting API keys by their |
| 48 | +creation date. This has been fixed. |
| 49 | + |
| 50 | +### Fix euid filter for meshUser endpoint |
| 51 | +**Audience:** Partner, Operator<br> |
| 52 | + |
| 53 | +#### Description |
| 54 | +Previously, the euid filter of the meshUser endpoint of the meshObject API |
| 55 | +did not work correctly. Instead of returning only users with a matching euid, |
| 56 | +all users were returned. This was fixed. |
| 57 | + |
| 58 | +### Tag Catalog Support for Users and Groups |
| 59 | +**Audience:** User<br> |
| 60 | + |
| 61 | +#### Description |
| 62 | +You can now define tag schemas for users and groups in the tag catalog. This enables you to create policies that |
| 63 | +enforce access rules for users and groups based on their tags, providing better compliance to your teams. |
| 64 | + |
| 65 | +#### How to use |
| 66 | +Navigate to the tag catalog in the administration area to create tag schemas for "User / Group" entities. Once |
| 67 | +defined, these schemas can be referenced in policies to create rules that automatically apply to users and |
| 68 | +groups based on their tag values. Note that user and group tags continue to be managed through the existing tag |
| 69 | +configuration and API. |
| 70 | + |
| 71 | +### Enforce User/Group Policies during Project Creation |
| 72 | +**Audience:** User<br> |
| 73 | + |
| 74 | +#### Description |
| 75 | +We enabled the project role policy evaluation during project creation. If a policy is |
| 76 | +defined between a project role and user/group then assignments can only be made to |
| 77 | +users/groups to the project if the relationship is compliant. |
| 78 | + |
| 79 | +### Improved User Authorization for Creation Flows |
| 80 | +**Audience:** User<br> |
| 81 | + |
| 82 | +#### Description |
| 83 | +In this release, we have redesigned the authorization flow to provide a more intuitive and efficient experience |
| 84 | +during workspace and project creation. Highlights include a streamlined dropdown interface, user-friendly role |
| 85 | +and expiration date pickers. This UI overhaul preserves all existing capabilities while improving usability |
| 86 | +and reducing friction during workspace and project creation. |
| 87 | + |
| 88 | +### Admin Area Button Stays White When Focused On |
| 89 | +**Audience:** Partner<br> |
| 90 | + |
| 91 | +#### Description |
| 92 | +The Admin Area button in the context navigation now maintains its white background color when focused on. |
| 93 | +This update enhances visual consistency and improves user experience by preventing the button from turning black during focus states. |
| 94 | + |
| 95 | +### Add Location Name In Platform Filter |
| 96 | +**Audience:** Partner<br> |
| 97 | + |
| 98 | +#### Description |
| 99 | +The location field has been added to platform filter in communication creation to improve platform identification. |
| 100 | +This change addresses issues where multiple platforms had the same name. |
| 101 | + |
| 102 | +### Deprecated Platform Notification Subscriptions |
| 103 | +**Audience:** User<br> |
| 104 | + |
| 105 | +#### Description |
| 106 | +The legacy platform notification subscriptions have been removed in user profile section. |
| 107 | +Users will no longer receive notifications through the old system, and all |
| 108 | +notifications should now be managed through the new Communication Center. |
| 109 | + |
| 110 | +### Deprecated Legacy Platform Notifications |
| 111 | +**Audience:** User<br> |
| 112 | + |
| 113 | +#### Description |
| 114 | +Legacy platform notifications have been deprecated and replaced with the Communication Center. |
| 115 | +When admin users attempt to send notifications to users through the legacy interface, they will |
| 116 | +now be shown a deprecation notice and redirected to the new Communication Center. |
| 117 | + |
| 118 | +### Deprecated Legacy Workspace Messages |
| 119 | +**Audience:** User<br> |
| 120 | + |
| 121 | +#### Description |
| 122 | +Legacy workspace messages have been deprecated and replaced with the Communication Center. |
| 123 | +When admin users attempt to send messages to workspace users through the legacy interface, they will |
| 124 | +now be shown a deprecation notice and redirected to the new Communication Center. |
| 125 | + |
| 126 | +### Accessible Label For Main Navigation Bar |
| 127 | +**Audience:** User<br> |
| 128 | + |
| 129 | +#### Description |
| 130 | +To support assistive technologies, like screen readers, |
| 131 | +we have added an accessible name ('Main Navigation') to the main navigation bar. |
| 132 | + |
0 commit comments