Is there any way to track the versions used by the nodes on the network and bump the minimum version when let’s say 75% of the nodes have upgraded to a version being rolled out? That should take care of any release stopping bugs (since rolling out would have been stopped earlier, ie at 50%) and gives plenty of buffer for nodes to upgrade and check if there are any bugs.
Yup, my node was restarted this morning–had to make an update to my stack–and I was regressed back to v1.99.3.
This behavious matches with what I explained here (Current rollout may lead to unexpected downgrades), and as BrightSilence pointed out here as well. As the minimum version pointer is 1.99.3 and the last rollout upgraded all nodes to 1.101.3, any container recreations (or stack updates) might result in downgrading to 1.99.3 (or if you are lucky ugprade to 1.102.3 if it has rolled out to that specific node)
And now it seems we are seeing unexpected and usually not tested downgrades as well:
This mess is unbelievable really.
It’s unrelated to this thread. I would move it.