>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3560196. --> Reported by: [norman.lol](https://www.drupal.org/user/2482808) Related to !144 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Version keys are more a core thing, to bust a scripts cache upon core version changes.</p> <p>If version omitted, the file hash will be generated automatically and by that every library change will be picked up automatically and cache busted automatically.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Remove the version lines from libraries.yml. By doing this, Drupal will use an automatically generated query string added to filenames. From the code documentation:</p> <blockquote><p>The string changes on every update or full cache flush, forcing browsers to load a new copy of the files as the URL changed.</p></blockquote> <p>See: <code>web/core/lib/Drupal/Core/Asset/JsCollectionRenderer.php:62</code></p> <p>The other option is to explicitly set the module's version on these lines and keep track of it when the version number changes/the asset is updated.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>