docs: Add migration guide for upgrading to Serverpod 3.5#563
Merged
Conversation
developerjamiu
added
documentation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new upgrade guide for moving Serverpod projects from 3.4 → 3.5 (Jetstream), and reorganizes older upgrade guides into a chronological archive while updating one inbound link to the pgvector upgrade page.
Changes:
- Add a new “Upgrade to 3.5” migration guide covering CLI/dependencies, migrations,
serverpod start, embedded Postgres vs Docker, agent skills, and deployment notes. - Move existing upgrade guides into
docs/11-upgrading/02-archive/and reorder them chronologically. - Update the Vector fields concept doc to point to the archived pgvector upgrade guide, and update the pgvector guide’s migration link.
Reviewed changes
Copilot reviewed 3 out of 9 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/11-upgrading/01-upgrade-to-three-five.md | New step-by-step upgrade guide for Serverpod 3.5. |
| docs/11-upgrading/02-archive/01-upgrade-to-one-point-two.md | Archived 1.2 upgrade guide after archive restructure. |
| docs/11-upgrading/02-archive/02-upgrade-to-two.md | Archived 2.0 upgrade guide after archive restructure. |
| docs/11-upgrading/02-archive/03-upgrade-from-mini.md | Archived Mini → full upgrade guide after archive restructure. |
| docs/11-upgrading/02-archive/04-upgrade-to-two-point-two.md | Archived 2.2 upgrade guide after archive restructure. |
| docs/11-upgrading/02-archive/05-upgrade-to-pgvector.md | Archived pgvector upgrade guide with updated migrations link. |
| docs/11-upgrading/02-archive/06-upgrade-to-three.md | Archived 3.0 upgrade guide after archive restructure. |
| docs/11-upgrading/02-archive/category.json | New archive category metadata for the upgrading section. |
| docs/06-concepts/02-models/03-vector-fields.md | Update link to the pgvector upgrade guide in its new archived location. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
marcelomendoncasoares
requested changes
Jun 1, 2026
Collaborator
marcelomendoncasoares
left a comment
marcelomendoncasoares
left a comment
There was a problem hiding this comment.
Nice work on the docs, @developerjamiu! Made some suggestions for improvement/completeness and only small corrections on the behavior of the features.
Swiftaxe
reviewed
Jun 2, 2026
Collaborator
Swiftaxe
left a comment
Swiftaxe
left a comment
There was a problem hiding this comment.
Looks really neat!
Added a couple of minor comments.
Collaborator
marcelomendoncasoares
left a comment
marcelomendoncasoares
left a comment
There was a problem hiding this comment.
Just a few comments more, but feel free to address or ignore as you consider relevant!
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
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.
Closes #537.
Adds a guide for upgrading an existing 3.4 project to 3.5 (Jetstream), covering the CLI bump, dependency pin, SDK constraint, schema migration, the new
serverpod startworkflow (with both embedded Postgres and Docker paths), agent skills, production-deployment notes, and a curated "What's new in 3.5".Files
docs/11-upgrading/01-upgrade-to-three-five.md.02-archive/(renamed from04-archive/), and the archive is reordered chronologically (oldest first) so1.2 → 2.0 → mini → 2.2 → pgvector → 3.0reads in the order they were created. The latest upgrade page (01-upgrade-to-three-five.md) sits at the top of the section to match the convention of "latest first" for the active upgrade.The new 3.5 guide pins to
3.5.0-beta.9while 3.5 is in beta.Verification
npm run buildpasses locally with no broken links.