docs: align protocol version status labels#1603
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the A2UI documentation and specifications to reflect the new versioning scheme, marking v0.8 as legacy, v0.9 as the previous stable release, and introducing v0.9.1 as the current production release. The reviewer's feedback suggests ensuring consistency across the documentation by updating remaining v0.9 references to v0.9.1, clarifying function execution boundaries, and adding links to the new v0.9.1 specification where appropriate.
adc1ef9 to
36f1cd6
Compare
|
(Possible dup of: #1419) |
36f1cd6 to
9d64bfd
Compare
9d64bfd to
ec60558
Compare
ditman
left a comment
There was a problem hiding this comment.
This LGTM, thanks for the tweaks!
gspencergoog
left a comment
There was a problem hiding this comment.
This looks good. At the least it is a good improvement.
| **Status:** Draft | ||
| **Status:** Stable | ||
| **Created:** Nov 20, 2025 | ||
| **Last Updated:** Dec 3, 2025 |
There was a problem hiding this comment.
Maybe we should just remove this line? Or at least replace it with the truth.
There was a problem hiding this comment.
Hmm yeah, might be simpler to just remove it, unless we get stuck in the same naming trap.
There was a problem hiding this comment.
To be clear: I was talking about the "Last Updated" line, not the status.
There was a problem hiding this comment.
Oh gotcha, the GitHub UI made that confusing for some reason.
There was a problem hiding this comment.
What’s the actual last updated date? Or want me to just remove it?
There was a problem hiding this comment.
Just remove it. If someone cares, it's right there in the git history.
Description
Follow-up to #1419. This fills the remaining v0.9.1 protocol-status gaps so the docs consistently identify v0.9.1 as the current production release, v0.9 as previous stable, v0.8 as legacy, and v1.0 as candidate.
Pre-launch Checklist