{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicvk6zfd75boyrmx7ra46aebg6h4374rimy5n635wwpi3rtoa2sti",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mf6dfkm3tky2"
  },
  "path": "/t/widget-uri-versioning-and-app-resubmission/1374584#post_1",
  "publishedAt": "2026-02-18T21:39:58.000Z",
  "site": "https://community.openai.com",
  "textContent": "In the Apps sdk docs the guidance is to implement versioning on the resource uri of the widget (ui.resourceUri or openai/outputTemplate)\n\n“ _Treat the URI as your cache key. When you update the markup or bundle, version the URI and update every reference to it (for example, the registerAppResource URI, _meta.ui.resourceUri in your tool descriptor, and the contents[].uri in your template list). ChatGPT honors _meta[“openai/outputTemplate”] as an OpenAI-specific compatibility alias._ ”\n\nYet the app submission guidelines indicate that\n\n“ _Once your app is published, tool names, signatures, and descriptions are locked for safety. To add or update your app’s tools or metadata, you must resubmit the app for review. Once your resubmission is approved, you can publish the update which will replace the previous version of your app._ ”\n\nWhat is the guidance for releasing a new version of my widget (and widget uri) on my mcp server yet staying protected from openai making a read resource request for the resource uri that is locked in the tool description of my submitted and approved app?",
  "title": "Widget uri versioning and app resubmission"
}