Fixed libraries should not use VERSION since that is always the Drupal core version.

@gilmord, thanks for the report!

And thanks for creating a separate issue, rather than continuing comment on an already closed issue.

Dropping this from Major to Normal priority, as it does appear there is a simple one-time deployment step workaround to resolve this, by clearing the cache entry for the file.

This caching issue isn't specific to this module, as it is pretty common for modules to use the VERSION keyword in *.libraries.yml files...but this current sets the version to the version of Drupal Core, rather than the module version.

I think most module maintainers expected that VERSION would be the module version, not Drupal Core version. But core code actually includes the comment:

// @todo Retrieve version of a non-core extension.

so it appears this has not been implemented.

See also: 🐛 Remove VERSION from libraries.yml Fixed , which resolves this same issue for another contrib module.

We'll be dropping the version attribute to avoid this issue going forward.

Automatically closed - issue fixed for 2 weeks with no activity.