Clarification on MCP Server URL and Versioning During ChatGPT App Update Submission

Sorry, what is the expected behavior regarding resource versioning? We noticed that resources were initially cached very aggressively (we actually thought they were simply stored as is), so we implemented a cache-busting mechanism by versioning resources (for example, by including a hash in the resource identifier). This approach worked well in the past: after submitting an app update, ChatGPT would eventually refresh the resource and start using the new version. Recently, however, we’re seeing resources being invalidated before the app submission is approved and rolled out. As a result, ChatGPT attempts to load a resource that is no longer available. Should we assume that tool descriptions are persisted once fetched, while resources are only cached temporarily and may be revalidated or refreshed independently of the app submission lifecycle?