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.

Proposed resolution

Remove the version number here: https://git.drupalcode.org/project/viewsreference/-/blob/8.x-2.x/viewsre...

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 viewsreference-3490686

Command icon 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:

About issue forks

Comments

trackleft2 created an issue. See original summary.

trackleft2 opened merge request !75

trackleft2’s picture

trackleft2
Primary language English
Location Tucson, AZ 🇺🇸
commented
Status: Active » Needs review
hosterholz’s picture

hosterholz
he/him
Primary language German
commented
Status: Needs review » Reviewed & tested by the community

MR !75 works.

scott_euser’s picture

scott_euser commented

Aha so its taking the Drupal Core version here, yet if the module is updated independently of core, its potentially an issue. Okay will merge, thanks!

scott_euser’s picture

scott_euser commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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