Release notes - May 2026

New features

Changelog – Custom filter events, AI context changes, and TM leverage

⭐ Two new events and one new category are now logged in the changelog, improving visibility and traceability across your projects:

• Custom filter changes are logged at the Team level: filter creation (including the filter name and the project in which it was created) and deletion (including the project from which the filter was deleted) will be captured in a log entry.

• Changes to project-level AI context are now logged at a Project level.

• A new changelog filter category "All TM Leverage Changes" has been added under "All Translation Changes", making it possible to isolate translations populated via TM application from manual inputs.

Improvements

Editor – Custom filter management restricted to Manager role and above

⚙️ Custom filters are shared across all projects within a team and are not attributed to an individual creator. To protect workflow-critical filters from unintended modifications, the ability to create, edit, and delete custom filters is now restricted to users with the Manager role or above. Users with the Translator or Reviewer role are still able to view and apply existing filters.

API – All routes now available under the GlobalLink Strings domain

⚙️ As part of the rebranding from Applanga to GlobalLink Strings, all API routes are now available under both the GlobalLink Strings and Applanga domains. Existing Applanga routes remain fully functional alongside the new routes with no planned deprecation, ensuring continuity for all current integrations.

Bug fixes

API – Status mapping for pseudo-translated strings

🛠 Previously, pseudo-translated strings were returned with the "In Order" status in API responses. The status is now correctly reflected as "Pseudo Translated" in the API response.

Editor – Strings marked as Outdated after import with no content change

💬 Users can update source strings on GL Strings at any point, either manually, via manual import or an integration. When the source string is updated, the existing translation (if it exists) is marked as Outdated.

🛠 Previously, if a user imported a file with an existing source string but didn't modify said source string, the translation would be still be marked as Outdated. Now, translations of unmodified source strings are no longer marked as Outdated.

Editor – Untranslated string counter displays the wrong value

🛠 In certain projects, the Untranslated string counter on the Project dashboard displayed the wrong value. The issue was caused by certain consecutive locking operations led to corrupted locked status metadata on the database level. The counter now displays the correct value, and locked language entries can no longer be created without a corresponding entry description.

Changelog – Export blocked when end date is not selected

🛠 Not selecting an end date in the changelog export dialog could result in a log export that covered an unintended date range. Both the start and end date fields are now required before the export can be initiated, and the Export button remains inactive until all required fields are filled in.