InsForge v2.1.6 changes storage download links to include a `?v=<etag>` version token, so updated artifacts no longer get masked by stale CDN caches and users are more likely to fetch the correct released files.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Introduced versioned artifact URLs for storage downloads by adding `?v=<etag>`, making URL identity reflect file revision and forcing cache refresh when content changes.
Operators and users downloading artifacts from InsForge through CDN paths will receive updated files more reliably after releases, reducing incidents where deployments use stale binaries or data. The implementation binds download URL versions to ETag values, so cache invalidation is tied to content changes instead of manual purge cycles. Watch whether any CDN layer or reverse proxy strips or ignores query parameters, and whether client-side download clients reuse cached responses outside normal validation paths.
Operators and users downloading artifacts from InsForge through CDN paths will receive updated files more reliably after releases, reducing incidents where deployments use stale binaries or data. The implementation binds download URL versions to ETag values, so cache invalidation is tied to content changes instead of manual purge cycles. Watch whether any CDN layer or reverse proxy strips or ignores query parameters, and whether client-side download clients reuse cached responses outside normal validation paths.