That is what I meant. Though I haven’t played with this part of the file to confirm how it would work or what instability might come from it. So the question remains, is this for the active graph, or a background file? If it’s the active graph we may have an issue. If it’s background stuff (ie updating the entire library) you could be good. My first edit would be to the package info, not moving stuff between packages though. Something like changing Clockwork 2.0 to Mechanical apparatus 2.0.
My gut says that the first list of GUIDS is where the dependencies are set though, so you’d really just want to reset those to the right version.
I believe Monocle has this already, and while you’d want to close the graph first, but the bulk upgraded tools I built and have shared here a few times will do this and a bit more. Like etransmit you’d want to not be in the file first though.