Version & Localisation management

I working on a complex Website project that already uses version management (Git for now - with testing, dev and live branches) and now needs to be localised for use in other countrys. The problem i encounter is, that the site or (subparts of it) will be constantly updated and these updates need to be localised as well. My problem is, that i dont find any concept (or maybe a pattern / system) that reflects this.

For example: I have a version 1.1 in my master language (e.g. english). Now i update a single file (in dev-branch of course). Maybe add some functions to the site. The new version would be 1.1.1 - it works, all would be fine - but now the localisation kicks in. that the localisation team should only get tested and working features is obviously. so they get that 1.1.1 state (wich maybe is already pushed to live system on the english site) and have to localise that. Assuming that they don´t finish this in one work day, or we got translation errors or something else, we got a new version number for localisation state. assuming that everything below 1.0 is in work and 1.0 and everything above this is completed or improved. And that is where i got lost. I dont find a good concept to handle that. I think if i create a new localisation branch for every change and language that will end up in a total mess of thousand branches.

So i looking for any advise that would help me to solve this. Maybe some tuts´s or books, concepts or whatever. Solutions that exclude Git are also possible.

Thanks for your help!