Release Notes

New Features

API – Set Max Character Length

💬 Up until now, teams could set a string's character limit for a specific language on the dashboard.

⭐ Now, teams that automate their workflow via our API can use this new endpoint to set a string's character limit in a given language, reducing manual steps.

You can find our more information about this new endpoint in our API documentation.

API – Retrieve Tag by Name

💬 Previously, to retrieve a tag ID based on a tag name, users had to retrieve all tag IDs via API and filter the results locally.

⭐ Now, a new endpoint allows users to pass a specific tag name and receive its ID, eliminating the need to process the full tag list. Requests that use tags for scoping will still require a tag ID, but finding that ID is now faster and more efficient.

CLI – Specify Tags in Push & Pull Actions

💬 Previously, pushing or pulling a subset of files required updating the CLI configuration each time.

⭐ Now, a new parameter allows you to request only files with specific tags for push or pull operations, without modifying the project’s configuration. This enables more targeted actions while keeping your configuration intact.

CLI – Set Tag Category on Push

💬 In large projects with many components or content sources, tags alone may not provide enough structure, making tag categories essential. Previously, assigning or updating a tag’s category required manual changes in the GL Strings dashboard.

⭐ Now, you can set a tag category directly via the CLI during push operations, enabling better organization without leaving your automated workflow.

Improvements

Custom Filter: Multiple Status Selection

💬 While reviewing your translations in GL Strings, you may need to view keys with multiple statuses at once (e.g., "Rejected" OR "Needs Review"). Previously, users could only filter by one status, which meant that users needed to use multiple filters.

⚙️ Now, users can select up to five workflow statuses in a single custom filter. The selection is preserved in the URL, making it easy to share and revisit the filtered view.

Language Batch Selection in Multilingual View

💬 Currently, users can select up to 50 projects in the Editor's multilingual view. Up until now, in projects with > 50 languages, users could select the first 50 languages with one click, but then had to select any additional languages one by one to include them in the multilingual view.

⚙️ Now, users can select languages in batches of 50.

Bug Fixes

User Group Permissions in Branching Projects

🛠 In branching projects, if a manager was part of a user group with limited language access (e.g., RU and DE only), they could still edit translations for all languages across all branches. This allowed managers to edit languages they weren't authorized to touch, which could lead to accidental or unauthorized content changes. We've enforced language restrictions in user groups across all branches, so that managers can only edit languages they have explicit permissions for.

Wrong Button Color in Dark Mode

🛠 On the Teams page, in dark mode, the Team Change Log button appears in an incorrect color that doesn't match the dark mode design system.

Screen Panel – Wrong Language for Upload in Dual Screen View

🛠 When in Dual Screen View, if a user changed the language in the right-hand dropdown to one that had no screen variant, then clicked Upload New Screen, the upload was incorrectly targeted at the previous language (from the breadcrumb) rather than the one currently selected in the dropdown. The setting now behaves as expected.

Project List – Shared Projects Section – Sorting Broken

🛠 In the Project List > Shared Projects section, sorting by Name or Creation Date didn't work when using the ascending/descending toggle. This is now fixed and it behaves as expected.