However, one thing that has always bothered me is when we say "well we're using ruby xx.xx (or node xx.xx or php xx.xx or whatever) on our development machines, so we must install that version on production" and then the hoops taken to do that. It should be "production can run ruby xx.xx so that's what you have to develop against".
I doubt that will ever be the case.
The main issue is, developers usually have a work backlog and those in charge have very little interest in what version everyone is running. If it already works on _a_ platform version, then chances are that the users will get better value for the developers time through adding another feature to the web app itself, than whatever benefits the upgrade or downgrade in platform version will bring.
You can try negotiating with the development team before the work commences though, or putting it in the initial delivery requirements if it is outsourced. It's just you would have to take initiative here, since nobody in your average business would consider operations to be a stakeholder until the system is live, so nobody is going to go out of their way ask you.