In the Apps sdk docs the guidance is to implement versioning on the resource uri of the widget (ui.resourceUri or openai/outputTemplate)
“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.”
Yet the app submission guidelines indicate that
“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.”
What 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?
If you think about this even a little bit more, doesn’t this mean that you have to version the complete MCP server interface and keep multiple versions around at the same time? One approved version that still works and another version that is waiting for approval. I guess this would be a almost impossible thing to do for most deployments out there. We really need a clear statement here.
Hello, New to this community! I have a similar problem, re-published the app and it is broken and unapproved. Does it mean that every time the time taken by open ai to approved the new vresion I will have broken app.
Can we expect openai people involved in this community to respond or this is just for enthusiasts?
We don’t do versioning on our widgets, does that mean if we redeploy our app with any new changes or fixes that do not involve the tools or metadata, would it be immediately live or we need to resubmit?
I would assume OpenAI blocks apps from making new pushes to the App without approval due to security concerns but not sure, with a cache/lock somehow . Our MCP is used in multiple platforms and if every time we make fixes or deployments we need to resubmit it will be an enormous pain.