Bump specification stable to v0.9 and draft to v0.10#1419
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the A2UI documentation to promote version 0.9 to stable and introduce version 0.10 as a draft. The changes include new specification files, updated protocol examples, and a reorganization of the documentation navigation structure. Review feedback identified several technical inaccuracies in the documentation, specifically regarding incorrect version references in section headers, copy-paste errors in legacy protocol descriptions, and malformed or missing examples for version 0.8.
selamw1
force-pushed
the
stable_ver_bump
branch
2 times, most recently
from
0543c57 to
86f0f0f
Compare
ditman
left a comment
ditman
left a comment
There was a problem hiding this comment.
I haven't reviewed the whole thing, but I think this is breaking the documentation by changing the header versions without moving the json messages around.
A simpler fix may be to just update the adjective next to the version numbers, so something like:
=== "v0.8 (Stable)"Would get changed to:
=== "v0.8 (Legacy)Then if we want to move the code blocks around, it should be easy.
Who'd be best to review this further, @zeroasterisk?
|
|
||
| - **`surfaceUpdate`**: Define or update UI components | ||
| - **`dataModelUpdate`**: Update application state | ||
| - **`beginRendering`**: Signal the client to render |
There was a problem hiding this comment.
Is the diff being weird? Otherwise this is wrong, I think that the messages that were under 0.9 earlier should be here now, because these are 0.8 right?
| > ``` | ||
| > | ||
| > This will ensure that all JS and CSS assets are inlined into the `index.html` file on build, making it ready to be served by your MCP server as a single resource. | ||
| !!! tip "Using Vite to inline" |
There was a problem hiding this comment.
What caused this reformat? Is this the prettier plugin?
| ### Example | ||
|
|
||
| === "v0.8 (Stable)" | ||
| === "v0.9 (Stable)" |
There was a problem hiding this comment.
Again, I don't think that updating the version numbers of the headers here is the right thing to do, because now the jsonl underneath doesn't match the version of the protocol on the title.
2 participants
Bumps the A2UI documentation and specification status to reflect version 0.9 as the latest stable release, version 0.10 as the active draft, and version 0.8 as legacy.
Proposed Changes
docs/specification/):mkdocs.yaml): Re-ordered navigation hierarchy under the Specifications node to place v0.9 (Stable) at the top.README.md): Updated version warning notice in root landing page to v0.9.Ref/Closes: #1374
Pre-launch Checklist