This release is huge. Quite often I write in these lines that we improved a lot that is not visible; I sometimes feel like I am struggling to showcase to you all the work that has been done in letters. Not with 5.14, because our amazing team of developers did a splendid job.
The migration of the frontend to Bootstrap 5 is mostly finished; just a bit of polishing will happen in the following versions. The grand positive is that we are now well-prepared for introducing significant UI improvements. And you can actually see what changed! Many operations are more swift and responsive already.
Another star of this release is the repository maintenance addition related to... Everyone knows them. Even with your best intentions, and smoothest workflows, they come and visit, not welcome. Merge conflicts. You can always solve them manually and be the deciding authority, but we are excited to share a powerful new button: Reset and reapply. This saves you from manual work, resetting Weblate's repository, and keeping the state of translations in the Weblate database, making Weblate the sole source of truth for translations.
Webhooks, the powerful communication of the machines making the work for us. Weblate got more skills with them when it comes to handling errors and also dropped some obsolete types. Most importantly, they are now exposed in the OpenAPI docs for easier use. This way, every Weblate instance has them handy at /api/docs/, like here for Hosted.
The last show pony in this round is the extended search options for DATETIME fields, helping you find the strings you page for.
And as this article is written in a stoppage time, I can tell you about today's release of 5.14.1 as well, with one security advisory fixed, string context logged, HTTP performance report, and more.
One community thing we want you to join is the discussion about supported databases. PostgreSQL really works the best, and the other, way less used options, are holding the development back. Come and tell us your opinion!
Why the stoppage time, you may ask. Well, there's a lot in the process, so expect the next blog post soon. In a few days!
