Actually it does which is kind of the point, it's just those conditions are fairly easy to meet. The TL;DR: version is that if you use LGPL code in your project you have to redistribute the source code of that LGPL code including copyright notices. In practice that requirement can usually be fulfilled by simply providing a link someplace convenient to wherever you original got the code from yourself so it's pretty easy to comply with. Additionally GPL and LGPL differ primarily in that GPL requires that code that uses it must itself be licensed under GPL, where as LGPL allows non-LGPL code to be linked to LGPL code (so long as the conditions of the LGPL code are still being met, primarily the distribution clause). The big difference between GPLv2 and GPLv3 was mostly about closing some loopholes that some companies (primarily TiVo) used to make it impossible to modify certain GPL code on their devices (mainly this involved using hardware DRM). This obviously violated the spirit of the GPL because the whole point is to allow for people to tinker with the code, and preventing that by coupling it to proprietary hardware as a end run around the GPL necessitated the creation of GPLv3 specifically to make doing that a violation of the license.
GPLv3 doesn't have any use conditions; it's free to use, for any purpose. You are probably thinking of the conditions on the things that aren't use - modification, distribution, etc.
If you've been using the repo for a long time and you didn't have a local copy to use in case github went down, etc, your deploy was already broken. Having local mirrors of third party repos, and pulling those into your build system is fairly trivial, and will save a lot of heartache in cases like this.
