Issue: Dynamically loaded Scripts NEVER Expire from CDN

It seems, that regardless of upgrade, which should change version numbers, timestamps, and all that good stuff CDNs like to use to determine if the cache is stale, dynamically loaded Javascript files do not include any of this info in the path. Thus, the Javascript in the CDN will never expire and read from the origin until max-age is reached. This means that any fixes, features, or other changes to Javascript between versions may not ever be seen if the scripts are loaded dynamically.

Fixed in the next release. VaultWiki will now always append the version number to the script path for dynamically loaded scripts.