Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Starting from Drupal 10.1.2, the version information within a library definition plays a critical role in generating a unique hash for aggregated files. Consequently, it is imperative that the "version" in a library definition is updated whenever a referenced CSS/JS file undergoes changes.
Alternatively, if the version is omitted, the prior behavior will apply, where the content of referenced CSS/JS files is utilized in the hash.
Incorrect usage of version information could lead to browser and edge cache invalidation issues.
See this update on the related changelog.
Steps to reproduce
Proposed resolution
Remove the version number here: https://git.drupalcode.org/project/environment_indicator/-/blob/4.x/envi...
Remaining tasks
Create a merge request to remove the version key.
User interface changes
N/A
API changes
N/A
Data model changes
N/A
Issue fork environment_indicator-3482961
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
trackleft2Comment #4
hitchshock+1
Files of the library have been updated several times, but the version hasn't been updated for a long time.
So, please, remove the library version or don't forget to update it every time the library files are updated.
I like the solution to remove the version.
So, RTBC.
Comment #6
trackleft2Comment #7
trackleft2Granting credit