If you look at the page Alexey posted, with the “PLEASE READ this thread” link… you’ll see upgrade deployment rates are controlled by the node checking https://version.storj.io/. As of when I post this you’ll see the automated system is working through a 1.125.2 → 1.126.2 update.
Eventually all nodes will be told to be on 1.126.2… and when they think it’s appropriate… they’ll start pushing to 1.127.x (unless a major issue is found: they can always skip problem releases)
(The open-source tagged releases are one thing… and the system that slowly tells nodes to upgrade to certain versions is separate)