Current documented procedure to manage the Drive client upgrade strategy :
assumes the customer will replicate the Nuxeo upgrade site and update the upgrade URL on the client-side. Or the clients must be told not to upgrade automatically.
This puts effectively Nuxeo in charge of managing the software landscape of customer productions.
In case of incompatibility or problems introduced by a later version, the default strategy is "next version". To implement "last working version and no automatic upgrade", the administrator must put in place the process documented above or act on the client-side to disable automated upgrade of clients...
What is requested is that the Administrator can force from a central place a given version of Drive on the client-side via configuration only. This would put the software landscape in production administrators hands in a simple and direct way.
E.g. leveraging the feature available in https://doc.nuxeo.com/client-apps/how-to-configure-nuxeo-drive-globally/ or equivalent mechanism...