Right now, when the "VERSION" is set for the version of a library within a module/theme, that library parser will use the Drupal VERSION constant, which is the current core version. It would be beneficial to have this version key off the module/theme version. This would allow the module/theme libraries to utilize the module/theme version for cache busting when the module is updated.
\
The library parser could use the module/theme version instead of the Drupal core version when available. Or it could also be adjusted to append the module version to the Drupal core version.
Active
11.0 🔥
asset library system
This seems similar to #2205027: VERSION in library declarations does not work for contributed/custom modules → . Can you verify if this is a duplicate?
I read the other issue and agree it is a duplicate. Since there hasn't been a response, I am going with that and closing this as duplicate.