We are excited to announce a significant enhancement to the /versions/latest/{filename} endpoint in our system. This update specifically addresses and significantly reduces caching issues (staleness) when fetching the latest version of raw package files.

What Was Happening Previously: When you requested package files from our Content Delivery Network (CDN), these files were subject to a caching time of 3600 seconds (1 hour). If you updated a package file, the latest version would not be immediately accessible. The endpoint would continue serving the file's cached (and therefore stale) version for up to an hour.

What Has Changed: We have now modified this behavior. The /versions/latest/{filename} endpoint will no longer serve cached files. Instead, it will redirect to the file's actual, current location. This change ensures that you consistently access the most recent version of a file without the previous delay.

Practical Example: For instance, if you hosted version 1.0 of a raw package file and then updated it to version 2.0, the latest endpoint would have continued to return the 1.0 version for at least 1 hour under the old system. With this enhancement, your first request will be redirected to the 1.0 file, and any subsequent requests (after the update) will be redirected to the 2.0 file.

Note / Action Required – Client Configuration: This enhancement relies on your client's ability to follow redirects. If you are using tools like curl without the -L flag, you might encounter issues, such as the appearance of downloading an empty file. To fully benefit from this update, please ensure your tooling is configured to follow redirects.

Thank you for your continued support. We are always here to assist with any questions or feedback regarding this update.

Help Documentation for Raw Package Files