Addressables Asset System: Stale Cache during Content Updates

Unity's Addressable Asset System utilizes a manifest to map asset keys to bundle URLs. When implementing a Content Update workflow, the system relies on bundle URL changes or specific cache policies to determine if a local asset is outdated.

There is uncertainty regarding the automatic invalidation of the local cache when the manifest version is incremented. While server-side Cache-Control headers can influence behavior, the Addressables API does not provide a client-side configuration to enforce max-age=0 or bypass the cache for specific updates without manually clearing the entire dependency cache.

Given the reliance on HTTP caching headers and manifest versioning in Unity 2024.x, the following points require clarification:

• Does a change in the manifest version automatically trigger the invalidation of associated local bundles?
• Is there a documented method to force a re-validation of specific bundles via DownloadDependenciesAsync without calling ClearDependencyCacheAsync?