Skip to content

Bump specification stable to v0.9 and draft to v0.10#1419

Merged
ditman merged 5 commits into
mainfrom
stable_ver_bump
Jun 11, 2026
Merged

Bump specification stable to v0.9 and draft to v0.10#1419
ditman merged 5 commits into
mainfrom
stable_ver_bump

Conversation

@selamw1

@selamw1 selamw1 commented May 12, 2026

Copy link
Copy Markdown
Collaborator

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

  • Specification Pages (docs/specification/):
    • Shifted v0.9 specifications and evolution guides to Stable status.
    • Shifted v0.8 pages and A2A extensions to Legacy status.
    • Created wrapper files for v0.10 as the new active Draft specifications.
  • Navigation Configuration (mkdocs.yaml): Re-ordered navigation hierarchy under the Specifications node to place v0.9 (Stable) at the top.
  • Site Documentation: Updated indices, roadmap, overview, quickstart, and what-is-a2ui example models to align references to v0.9 stable features.
  • GitHub Repository Landing (README.md): Updated version warning notice in root landing page to v0.9.

Ref/Closes: #1374

Pre-launch Checklist

  • I signed the [CLA].
  • I read the [Contributors Guide].
  • I read the [Style Guide].
  • I have added updates to the [CHANGELOG].
  • I updated/added relevant documentation.
  • My code changes (if any) have tests.
  • If my branch is on fork, I have verified that scripts/e2e_test.sh passes.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread docs/concepts/overview.md Outdated
Comment thread docs/concepts/overview.md Outdated
Comment thread docs/introduction/what-is-a2ui.md Outdated
Comment thread docs/quickstart.md Outdated
@selamw1 selamw1 force-pushed the stable_ver_bump branch 3 times, most recently from 86f0f0f to ac352f8 Compare May 12, 2026 22:21

@ditman ditman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Comment thread docs/concepts/overview.md Outdated
Comment thread docs/guides/a2ui-in-mcp-apps.md Outdated
Comment thread docs/introduction/what-is-a2ui.md Outdated
@selamw1 selamw1 force-pushed the stable_ver_bump branch from c56f5a9 to a8055cb Compare June 9, 2026 21:13
@selamw1

selamw1 commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator Author

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?

Agreed. I have aligned the version tabs with their correct payload versions by updating only the version adjectives (e.g., changing v0.8 (Stable) to v0.8 (Legacy) and v0.9 to v0.9 (Stable)).

Additionally:

  • Removed the obsolete v0.10 draft stubs and references, updating draft/candidate links to v1.0 (Candidate).
  • Cleaned up redundant tabs and payloads in docs/quickstart.md.

@ditman ditman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM! Thanks for the changes!

Comment thread docs/guides/a2ui-in-mcp-apps.md
@samjulien

Copy link
Copy Markdown

Hi all, I didn't see this PR and opened #1603 today. I diffed the two and there is definitely overlap around the broad v0.8/v0.9 status cleanup in the README and docs wrappers.

The specific gaps I see are that this PR does not cover the remaining v0.9.1 current-production corrections. In particular, #1603 updates specification/v0_9_1/README.md and specification/v0_9_1/docs/a2ui_protocol.md, where the v0.9.1 spec still refers to itself as v0.9 / Draft and uses v0.9 example payloads/catalog URLs. It also updates the quickstart and intro examples from v0.9 / specification/v0_9/... to v0.9.1 / specification/v0_9_1/..., updates specification/v0_9/docs/a2ui_protocol.md from Draft to Previous Stable, and adjusts the v0.8/v0.9 wrapper pages to point readers to v0.9.1 as the current production spec rather than treating v0.9 as current stable.

Suggest we either fold those remaining v0.9.1-specific fixes into this PR, or this PR can land first and I can narrow/rescope #1603 as a follow-up that only addresses the remaining v0.9.1 current-production references and examples. Either is fine with me!

@ditman ditman merged commit c89186b into main Jun 11, 2026
19 checks passed
@ditman ditman deleted the stable_ver_bump branch June 11, 2026 00:40
@github-project-automation github-project-automation Bot moved this from Todo to Done in A2UI Jun 11, 2026
@ditman

ditman commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

OK @samjulien, I landed this because it had been brewing for a while already. Feel free to rebase your PR and add the missing details there!

Thanks for your contribution (and patience), @selamw1!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stable version bump (0.8 -> 0.9) needed in docs

3 participants