docs: reference rc.9 and v1.0.0 release dates#628
Draft
johnleider wants to merge 1 commit into
Draft
Conversation
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.
Updates docs and the v1.0.0 GitHub milestone to reference the scheduled release window:
Changes
roadmap.md—DocsTimeline: v1 dateQ3 2026→July 22, 2026; rc entry + intro prose note the final rc.9 cut on July 21.AppBanner.vue— site banner now announces the July 22 stable release instead of the generic "now a release candidate".why-vuetify0.md— Road-to-v1 line(Q3 2026)→(July 22, 2026).README.md(packages/0, root symlink) — @rc install note + contributing section reference the July 22 stable date.guide/tooling/vuetify-cli.md— example version1.0.0-rc.8→1.0.0-rc.9.Also updated out-of-band (not in this diff): the v1.0.0 GitHub milestone description now reads "stable release scheduled 2026-07-22" with the rc.9/July-21 detail — this drives the "Now" block of the docs roadmap live via the GitHub milestones API.
All copy is future-tense/scheduled (today is 2026-07-16); nothing claims the stable release has shipped.
Not touched (flagged, out of scope):
constants/releases.tsRELEASE_ALIASES (no rc/1.0.0 alias — renders raw, fine);constants.mdexample version string;devkey.mdhistorical alpha framing.