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

Hi @casey-chow , Is there a way to get the draft version in advanced (corresponding to pre-release version) via ‘client version’? We have breaking change in the same tool input/output schema which need reliable version to route to the correct mcp server upstream. Currently we use URI Path-Based Versioning but the submission page is having a bug on oauth which don’t allow us to change the URI path. We also try to get the clientInfo.version but it seems “Scan tools” at draft time always send the previous version (1.0.0 for our case). Is it possible to create version for draft to make it more reliable to detect clientInfo.version prelease? Thanks,