Skip to content

docs: update note on EOL for AS4#8215

Open
mabuyo wants to merge 1 commit into
mainfrom
docs/migration-note
Open

docs: update note on EOL for AS4#8215
mabuyo wants to merge 1 commit into
mainfrom
docs/migration-note

Conversation

@mabuyo

@mabuyo mabuyo commented May 21, 2026

Copy link
Copy Markdown
Contributor

Update note on landing page to note v4 EOL date.

Summary by CodeRabbit

  • Documentation
    • Updated Apollo Server introduction with upgrade recommendations for users on prior versions.
    • Clarified Apollo Server 4 end-of-life date (January 26, 2026).
    • Added migration guide links for v4→v5 and v3→v5 migration paths.

Review Change Stack

@mabuyo mabuyo requested review from a team and glasser as code owners May 21, 2026 00:19
@apollo-librarian

apollo-librarian Bot commented May 21, 2026

Copy link
Copy Markdown

✅ Docs preview ready

The preview is ready to be viewed. View the preview

File Changes

0 new, 1 changed, 0 removed
* (developer-tools)/apollo-server/(latest)/index.mdx

Build ID: 21c52d8aab143f296ce10421
Build Logs: View logs

URL: https://www.apollographql.com/docs/deploy-preview/21c52d8aab143f296ce10421


⚠️ AI Style Review — 1 Issue Found

Summary

The pull request updates the documentation style guide with the following changes: for 'framing-apollo-products', it suggests using simpler terms like 'move' or 'adopt' instead of 'migration'; in 'framing', 'Apollo' replaces 'We' for clarity; for 'structural-elements', admonitions are now required for end-of-life warnings; 'text-formatting' now mandates descriptive noun phrases for link text; 'verb-tense-and-voice' requires active voice for Apollo Server 4 status; the 'voice' section encourages a more authoritative tone; and 'word-and-symbol-usage' restricts the use of 'since' to time-based contexts only.

Duration: 2264ms
Review Log: View detailed log

This review is AI-generated. Please use common sense when accepting these suggestions, as they may not always be accurate or appropriate for your specific context.

@coderabbitai

coderabbitai Bot commented May 21, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 40dbbaf5-b6ce-4db0-8736-d36cd9a9891b

📥 Commits

Reviewing files that changed from the base of the PR and between cfbfe71 and 9be4db1.

📒 Files selected for processing (1)
  • docs/source/index.mdx
📜 Recent review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Docs Deploy Preview
🧰 Additional context used
🪛 GitHub Check: AI Style Review
docs/source/index.mdx

[warning] 11-11: docs/source/index.mdx#L11
Framing Apollo Products: Use simpler language like 'move' or 'adopt' instead of 'upgrade' or 'migration' where possible.

Framing: Use 'Apollo' instead of 'We' to clearly identify the entity making the recommendation.

Structural Elements: Use a admonition for highly important information like end-of-life warnings instead of a blockquote.

Text Formatting: Avoid using vague phrases like 'previous versions' as link text; use a rich noun phrase instead.

Verb Tense and Voice: Use active voice to describe the status of Apollo Server 4.

Voice: Use a more authoritative and encouraging tone rather than just recommending.

Word and Symbol Usage: Avoid using 'since' as a synonym for 'because'.

> We recommend that all users of [previous versions](./previous-versions) of Apollo Server move to Apollo Server 5 as soon as possible. Apollo Server 4 has been end-of-life since January 26, 2026. Refer to the [adoption guide for v4](/apollo-server/migration/) or [v3](/apollo-server/migration-from-v3/).
🔇 Additional comments (1)
docs/source/index.mdx (1)

11-11: LGTM!


📝 Walkthrough

Walkthrough

The Apollo Server documentation introduction page updates its version guidance to recommend upgrading to Apollo Server 5, explicitly states Apollo Server 4 reached end-of-life on January 26, 2026, and provides direct links to migration guides for users on v3 or v4.

Changes

Documentation updates

Layer / File(s) Summary
Version upgrade guidance in intro
docs/source/index.mdx
Introduction page messaging replaces older Apollo Server 3 end-of-life guidance with a notice recommending Apollo Server 5 upgrade, Apollo Server 4 end-of-life timestamp (January 26, 2026), and links to v4→v5 and v3→v5 migration guides.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: update note on EOL for AS4' accurately and concisely describes the main change: updating documentation with Apollo Server 4's end-of-life information.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/migration-note

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codesandbox-ci

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Comment thread docs/source/index.mdx
@@ -8,7 +8,7 @@ description: Learn how Apollo Server simplifies building GraphQL APIs with its s
>
> Apollo Server 5 is a small upgrade focused largely on adjusting which dependency versions are supported. [Upgrading from v4 to v5](/apollo-server/migration/) usually only takes a few minutes. Because the behavior of Apollo Server has changed minimally between v4 and v5, these docs document both versions.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mabuyo I just want to confirm that you think this paragraph still makes sense as written

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I think it still stands! We are going to discuss possibly splitting off v4 and v5 though to further reduce confusion on v4 being EOL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants