This issue is a followup toand .
It has been proposed that modules will use the latest core libraries unless they explicitly declare a specific library version with
Calls to drupal_add_library() don't specify version, just the library. If you want a specific version, register your own custom library in hook_library_info(), list the dependency that JS code has, and then call drupal_add_library() of that custom library. --
If a module pins itself to a library version, Core should warn a site maintainer when a library required by a module has been up-versioned beyond the max version allowed by the module.
The module should not be disabled nor should enabling it be prohibited. The module might work without issue with a later version of a required library. But a site maintainer should be made aware that an element of their site is behind the latest version of some required component.