Library should not be using the Drupal VERSION for the version

Created on 19 November 2024, about 1 month ago

Problem/Motivation

This leaves the assets in a state where they're strongly linked to the Drupal core version rather than independent and randomly generated by a cache clear.

Steps to reproduce

View the assets on the front end, and they'll have the Drupal version attached as cache busting query strings.

Proposed resolution

Remove the version: VERSION declarations from the eu_cookie_compliance.libraries.yml file.

Remaining tasks

Provide issue fork.

User interface changes

N/A

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024