docs: Update upgrade guide to 4.0#603
Open
Zfinix wants to merge 1 commit into
Open
Conversation
Swiftaxe
reviewed
Jun 15, 2026
Swiftaxe
left a comment
Swiftaxe
left a comment
Collaborator
There was a problem hiding this comment.
Looks good!
One thing left: The guide is missing how to set up the MCP servers. This is done automatically when creating new serverpod projects, but when upgrading it is currently manual, unless we offer a command to run in the CLI.
It says: "Some editors, like Cursor, require enabling the MCP server in their settings.", but the user gets no help in how to set this up for their IDE, and has to research this themselves.
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
2 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.
Summary
Updates the upgrade guide from 3.5 to 4.0 (title, headings, prose, version pins, and the migration tag). The 3.4 from-version and the Dart SDK constraints are left unchanged.
The filename and URL slug keep
upgrade-to-three-fiveso the existing inbound links from the legacy-auth guide don't break. Happy to rename the file in a follow-up if we want the URL to match.Part of #584