Apollo Router v1 Unsupported — when and how should I migrate?
GraphQL platform teams running Apollo Router v1 need to choose an upgrade target now that Router v1 and Federation v2.9 are out of support after March 31, 2026.
Blockers
- package/apollo-router-v1 — EOL 2026-03-31
- package/apollo-federation-v2-9 — EOL 2026-03-31
- requires_version: package/apollo-router-v2-10 → package/apollo-federation-v2-12
- v2.10 is the supported upgrade target after v2.9 is out of support
- latest v2.x is positioned as the upgrade path after Router v1 support ended
Who this is for
- high-scale
- enterprise
- microservices
- compliance
Candidates
Upgrade to GraphOS Router v2.10 LTS with Federation v2.12
As of 2026-04-02, Router v1.x, including v1.61.x LTS, and Federation v2.9 are already out of support as of March 31, 2026. Apollo states Router v2.10 with Federation v2.12 was released as the next LTS on December 12, 2025 and is supported until September 2026. Apollo explicitly positions v2.10 as the stable upgrade target for teams leaving v1.x and says teams already on Federation v2 do not need subgraph changes, but must update composition settings to a supported Federation version. Apollo's release lifecycle table marks v2.10 as LTS with no Premier Support extension available.
When to choose
Use this when you want the lowest-change supported landing zone after the March 31, 2026 cutoff, especially for enterprise, compliance, or freeze-driven environments. It is the best fit when operational stability matters more than getting the newest v2.x features.
Tradeoffs
Best support predictability and Apollo-recommended migration target from v1.x, but it has a shorter runway than future LTS lines and will not receive the newest minor-line features.
Cautions
Do not treat this as a zero-work version bump if your supergraph still depends on Federation v1.x, because Router v1.60+ and all Router v2 releases do not support Federation v1.x supergraphs. Also note that Router v2.10 support ends in September 2026, so this can be a stabilization step rather than a long-duration resting place.
Upgrade to the latest GraphOS Router v2.x release
As of 2026-04-02, the latest GraphOS Router release on Apollo's official GitHub releases page is v2.13.0, published on March 31, 2026. Apollo says the v2.x line remains under active development with future feature releases and new minor versions, while older branches only get LTS fixes if designated. This path keeps you closest to current fixes and capabilities instead of pinning to the December 2025 LTS cut. For GraphOS-managed usage, Apollo's pricing page shows self-hosted GraphOS Router is included across plans, with Free limited to 60 requests per minute and Developer starting at $5 per million requests as of 2026-04-02.
When to choose
Use this when you want the newest v2.x features and fixes immediately and can absorb a faster upgrade cadence. It is the better choice for platform teams already comfortable tracking Apollo minor releases rather than anchoring on a fixed LTS.
Tradeoffs
You get the freshest functionality and fixes, but you accept more release churn and less of the change-freeze predictability that drove Apollo to publish LTS lines.
Cautions
The same Federation caveat applies here: Router v2 does not support Federation v1.x supergraphs, so legacy Federation 1 users need a composition migration first. If you want long support windows with fewer upgrades, latest v2.x is the wrong operating model compared with an LTS target.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Apollo Router v1 Unsupported — when and how should I migrate?"