I wonder if this could be cause by an update of the LESS parser that now understands this CSS while it might have just treated it as an opaque string before.

That was my first reflex too, but the less engine we have on 14.10.18 (1.17.2) is 7 years old.