While not strictly necessary, finding the minimum viable version numbers for the dependencies just seems less arbitrary than "whatever was most current when we added it". Not sure if there's an automated tool to do binary search across version numbers and run tests until it fails, but that's what we should do.
While not strictly necessary, finding the minimum viable version numbers for the dependencies just seems less arbitrary than "whatever was most current when we added it". Not sure if there's an automated tool to do binary search across version numbers and run tests until it fails, but that's what we should do.