Version the documentation section alongside the specification - #2990
Merged
mcp-commander[bot] merged 4 commits intoJul 10, 2026
Conversation
a-akimov
approved these changes
Jun 30, 2026
a-akimov
left a comment
Contributor
There was a problem hiding this comment.
I have reviewed it, was not able to find any problems. Overall, very exicted to see that we are introducing versioning for docs as well as they should reflect what's in a corresponding specificaiton version.
Happy to approve it; but would be great if @olaservo and @cliffhall could look at this as well.
Member
|
@claude review |
Contributor
|
@localden would it be possible for you to merge these changes soon? This would greatly help us start updating the docs & tutorials for the new spec version. |
The Documentation tab now uses the same Mintlify version picker as the Specification tab. The current guides move to docs/docs/2026-07-28/ as the canonical, in-progress version, and identical snapshots are stored under 2025-11-25, 2025-06-18, 2025-03-26, and 2024-11-05 so every released spec version has matching docs. No content backfill: the snapshots are a copy of today's docs. Internal links inside each versioned tree point within that version. Old unversioned /docs/ URLs redirect to the 2026-07-28 pages, and a /docs/latest alias mirrors /specification/latest so links and the warning banner survive future version bumps. The spec version warning script is generalized to also show a banner on older docs versions. Version labels are chosen so the picker entries unify with the Specification tab when cut-release.yml promotes the draft spec to 2026-07-28 on this branch. :house: Remote-Dev: homespace
Replace the docs/docs/2026-07-28 directory with docs/docs/draft so the Documentation tab mirrors the Specification tab exactly: dated released versions plus a Draft entry. Both tabs now share identical version labels, so the picker unifies immediately instead of after the cut. Unversioned /docs/... URLs and /docs/latest now point at the latest released version (2025-11-25), matching the spec's redirect semantics. cut-release.yml promotes docs/docs/draft alongside the spec draft: copies it to docs/docs/<version>, rewrites internal links, patches the Documentation tab nav, retargets the latest-alias and legacy redirects (including /specification/latest, which was never retargeted), and adds dated siblings for draft-source redirects. Also fixes the promoted version being inserted after older versions instead of first. :house: Remote-Dev: homespace
🏠 Remote-Dev: homespace
…base During the rebase onto docs/2026-07-28-release, git's rename detection paired the old docs/docs/* paths only with the 2025-06-18 snapshot, so docs edits that landed on the base branch (Rust client tutorial, Claude Desktop connector UI text, requestedSchema fix, Kotlin SDK tier, auth sample link, OAuth URL validation guidance) were merged into that copy alone. Copy the merged 2025-06-18 files over draft, 2025-11-25, 2025-03-26, and 2024-11-05 with internal links rewritten to each version's prefix, keeping all snapshots identical per the PR's intent. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N5Z3TGJTN8cH6goHhdekqc
claude
Bot
force-pushed
the
localden/versioned-docs
branch
from
July 10, 2026 05:16
fbfacad to
992e926
Compare
Contributor
Author
|
/lgtm force |
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
4 participants
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.
Adds the same Mintlify version picker to the Documentation tab that the Specification tab already has. The two tabs use identical version entries (released dated versions plus Draft), so the picker is unified from day one.
docs/docs/draft/(git renames fromdocs/docs/), mirroringdocs/specification/draft/. Identical snapshots of today's docs sit under the four released versions; no content backfill, per plan./docs/...URLs and a new/docs/latestalias (mirroring/specification/latest) redirect to the latest released version,2025-11-25.spec-version-warning.jsgeneralized intoversion-warning.js: older docs versions get the "older version" banner, draft docs get a draft notice, both resolved through thelatestredirects so no updates are needed per release.cut-release.ymlnow promotesdocs/docs/draft/alongside the spec draft at final cut: copies it todocs/docs/<version>, rewrites internal links, patches the Documentation tab nav, and retargets thelatest-alias and legacy redirects (including/specification/latest, which the workflow previously never retargeted). It also now inserts the promoted version first in the picker instead of after the older versions.npm run prepis clean, includingmint broken-linksacross the redirects. The cut-release nav patch was dry-run locally against the newdocs.json: it produces unified pickers with2026-07-28 (latest)first on both tabs and correctly retargeted redirects.