From my understanding (more knowledgeable staff, jump in and correct me if I’m wrong) that is the correct minimal version to not be disqualified… basically it is the minimal version that would allow for egress I believe. Once you’re behind that you’re too far back for the node to function as a part of the network. What you’re interested in is the minimal version for ingress, which I think is two updates back from current? I don’t believe this is an actual number back, like “current version - 0.2” or something, but rather number of times a new version has been pushed. Using random sequential numbers for example, if there were updates in the order of 1.22.1, 1.22.4, 1.23.1, 1.26.3 with 1.26.3 being current then I think at 1.22.4 you would still see ingress but at 1.22.1 it would be egress only.
I had suggested this tooltip be better defined, I’d encourage you to go and vote for it here: Improved version tooltip on dashboard
If you’re not auto updating then I’d advise watching the Product Discussions section of the forums for changelog advisories, or watching version.storj.io as Trooper suggested, although I don’t think the storagenode/minimum/version value is truly the minimum allowed as they suggest. The key values to watch in my opinion are storagenode/suggested/version as this will be what is current and storagenode/suggested/rollout/cursor as this indicates when the Docker images (what I’m using) will be released. When the cursor value goes to all f’s the image should be up on Docker for pull.