docs: prepare for stable 3.0 release - #1073
Merged
Merged
Conversation
DaleSeo
marked this pull request as ready for review
July 28, 2026 18:05
alexhancock
approved these changes
Jul 28, 2026
This was referenced Jul 28, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
The
2026-07-28spec is now live, so documentation should link to that stable version instead of the moving draft. The README should also direct users to the current 3.x migration guide and describe the specification as stable ahead of the 3.0 release.How Has This Been Tested?
Breaking Changes
None.
Types of changes
Checklist