Files
Max Isbey 59c066dfce Present v2 as the stable release across the README, docs, and policies
The README, the get-started docs, the What's new page, SECURITY.md, and
the contributor docs all still described v2 as a pre-release: pin an
exact 2.0.0b1, do not use in production, v1.x is the only stable line.
This flips that framing for the stable release. Install lines become
plain `mcp[cli]` (the launch-command page keeps only the exact pin that
`mcp install` itself writes), the pre-release banners and pin warnings
go away, the What's new page drops its beta note and the two stale
"since 2.0.0bN" provenance markers, and SECURITY.md gains a
supported-versions table (2.x current, 1.28.x maintenance).

v1.x is presented as the maintenance line throughout, with its docs at
/v1/ and a `<2` bound for projects that are not ready to migrate. The
branching-model text in AGENTS.md and CONTRIBUTING.md now describes main
as the stable line, and the v2 feedback issue template loses its
pre-release wording and the v2-alpha label.

No-Verification-Needed: doc-only
2026-07-26 09:41:35 +00:00
..