What happened?
It seems that using jsDelivr with the @latest tag is no longer working as expected. Requests that previously returned the latest asset now trigger HTTP 301 redirects, seemingly originating from Cloudflare.
How to reproduce it
Steps to reproduce the behavior:
- The following URL, which should return the latest version of config.json, instead responds with a 301 redirect:
HTTP/2 301 Moved Permanently
Date: Wed, 13 May 2026 16:21:00 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 90
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: *
Timing-Allow-Origin: *
Cache-Control: public, max-age=31536000
Cross-Origin-Resource-Policy: cross-origin
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Location: /gh/silverhack/monkey365assets@latest/assets/config.json
Accept-Ranges: bytes
X-Served-By: cache-fra-eddf8230044-FRA, cache-mrs10527-MRS
X-Cache: HIT, MISS
Vary: Accept-Encoding, Accept
Alt-Svc: h3=":443"; ma=86400
Nel: {"report_to":"cf-nel","success_fraction":0.01,"max_age":604800}
Age: 576900
Cf-Cache-Status: HIT
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s="}]}
Server: cloudflareExpected behavior
@latest should resolve to the most recent release or commit- Monkey365 assets should be served directly without redirection loops or Cloudflare‑level redirects
Additional context
What happened?
It seems that using
jsDelivrwith the@latesttag is no longer working as expected. Requests that previously returned the latest asset now trigger HTTP 301 redirects, seemingly originating from Cloudflare.How to reproduce it
Steps to reproduce the behavior:
Expected behavior
@latestshould resolve to the most recent release or commitAdditional context
jsDelivrdocumentation, using latest is not recommended for production usage