This version can truly be called major, not just for its number. Let’s walk through the additions and improvements our committed team and amazing community contributors delivered.
The shiniest new feature is bringing more options into automatic translation configuration. Machine translation engines are getting more capable, so why not use them better as a help for your human translators? You might want to check the new standard, even if you don’t want to change anything. The default setting of the source language has changed!
Then we have a new add-on, Weblate now speaks webhooks! Want some of your other platforms to listen to Weblate? Set it up!
The API got better again with this release, so if you like to instruct your Weblate this way, definitely check out the full list of changes this time. There are new calls as well as OpenAPI Specification 3.1.1 being used to generate the schema for our REST API.
And it would not be the right blog post without mentioning boosted performance. So, quickly, we can say that Translation Propagation and Component Discovery as well are now…quicker and less resource-hungry.
Last, but not least, bug fixes. Nothing huge this time, but important they are. If any of the reasons above did not lure you into upgrading, a fixed CVE-2025-32021 should do. We are not aware of any exploitation of this, and the severity is low, but keeping a known security issue in your infra? No! So what happened?
When creating a new component by cloning an existing one that has a VCS URL specified in settings, this URL was included in the client's URL parameters during the creation process. Quite a rare event to be caught in, but better to have it covered, right?
So that’s it with 5.11. All Weblate Cloud users are getting it now, and Hosted Weblate is running it already. Should you want any help with the configuration or upgrades, we will happily help!
If not sooner, see you with 5.12 in mid-June.
