Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This issue is a followup to #1787222: [meta] Strategy for updating vendor JS libraries within a major stable version and #1810352: Support version detection of core libraries when implemented through drupal_process_attached (drupal_add_library).
It has been proposed that modules will use the latest core libraries unless they explicitly declare a specific library version with hook_library_info
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. -- #1787222-38: [meta] Strategy for updating vendor JS libraries within a major stable version
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.
Comments
Comment #1
valthebaldDoes this belong to core or d.o. issue queue?
Comment #12
nod_Since we don't ship popular librairies we didn't run into this and contrib isn't asking for it.