Description
Description
At time of this writing, the following two URLs resolve to different versions of the same library, though it seems like they should resolve to the same version:
That is, at time of writing, that should be resolving to version 11.21.1.
But as you can see in these screenshots, the first one resolves still to 11.21.0, whereas the second one resolves to 11.21.1. I made sure to do so with devtools open to disable the cache and ensure that the latest version of the file was pulled from the CDN.
I'm sure this is because 11.21.1 was released a few hours ago, and there's some inconsistent version caching/updating going on, on the CDN's side. I know the docs say it's 7 days for version aliases, but... in this case, one of them updated nearly immediately and the other didn't.
I'd just like clarification on what those windows are (for different types of version aliases)... like how long do you have to wait to make sure that all relevant URLs resolve to the same new version?
I imagine by the time this is triaged, both URLs will have been updated to the newest version, so it won't be reproducible. But that's why I included the screenshots. :)
Affected jsDelivr links
https://cdn.jsdelivr.net/npm/sweetalert2@11
https://cdn.jsdelivr.net/npm/[email protected]
Response headers
accept-ranges bytes
access-control-allow-origin *
access-control-expose-headers *
age 327
alt-svc h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
cache-control public, max-age=604800, s-maxage=43200
content-encoding br
content-length 21002
content-type application/javascript; charset=utf-8
cross-origin-resource-policy cross-origin
date Fri, 16 May 2025 22:29:19 GMT
etag W/"12baa-aOKjr3lpvrhehZO4RdpMsNEMCJ8"
strict-transport-security max-age=31536000; includeSubDomains; preload
timing-allow-origin *
vary Accept-Encoding
x-cache MISS, HIT
x-content-type-options nosniff
x-jsd-version 11.21.1
x-jsd-version-type version
x-served-by cache-fra-etou8220171-FRA, cache-dfw-kdfw8210124-DFW
Information
- Device OS: Windows 11
- Browser & Version: Chrome 136.0.7103.93
- Your location: Texas/USA
Requisites
- I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
- I checked the documentation to understand that the issue I am reporting is not normal behavior.
- I understand that not filling out this template correctly will lead to the issue being closed.
Additional content
No response