Updating just because their is a newer version of language or new tool has arrived is seriously foolish. It requires a lot of effort in migrating / testing when your code base is big.
Companies don't usually change versions / tools untill their is a major breakthrough or external requirement.
I'm working on a project that still uses Java 6, Spring 3.x and Angular 1.x while almost 3 iterations of all languages / tools have arrived in the market. ( Their are still no issues in usability, scalibity or any bottleneck with older stack )
Though we are also migrating the same to latest market standards due to customer demand but, that made project to hire new team of 20 + new developers.
Though in our case, our older code is mostly non- compatible with the new versions of framework /libraries.. we decided to rewrite it completely. Started with the major user facing part and developed incremently.