Is there a way to update the ?v= parameter after updating the library files, to help cache-bust library files in CDN environments? For example: <script src="/libraries/fontawesome/js/fontawesome.min.js?v=6.1.0" defer></script>
I updated /libraries/fontawesome/* over a month ago. No regressions, but icons introduced with the new library are not found (you see only the dotted-line question/exclamation mark) ONLY in the LIVE environment. Dev/Test environments (no caching, no CDN) do not have this problem. I confirmed LIVE Drupal environment has the latest file versions, the deployment succeeded. I have cleared all caches available to me multiple times. NOTE: I do not have access to clear Pantheon's Global CDN cache. In my browser debugger, if I select 'Disable cache', it usually downloads the newer library and the icon will render, but of course that fix is just for me in that one browser. All other users still get the stale file version. All signs point to a CDN-to-browser caching issue. Query params of course are one cache-busting strategy.
Just wondering if there was a way to tweak the 'v=' value anytime a new library is installed?
1. Update /libraries/fontawesome/* to the latest versions downloaded from fontawesome web site
2. Deploy to live environment & clear caches
EXPECTED: new *.js file versions are in effect
ACTUAL: new *.js file versions are in effect in dev/test, but in LIVE, browsers think they have the latest but do not
Active
2.24
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The problem is not just the CSS files. Also font files normally get cached. If you use custom font awesome font kits newer versions will not be loaded so this version parameter should also be included loading the font files itself.