serverpod-upgrading

To upgrade Serverpod safely, update all pinned dependencies consistently across server, client, Flutter, and shared packages, run pub upgrade, regenerate code, and create database migrations. This coordinated sequence prevents build breaks and API failures.

Migrating Serverpod from v2.x to v3.0 introduces breaking changes in the Relic web server, Session handling, enum serialization, model APIs, and authentication. You must analyze your project and explicitly remediate these documented breaking changes.

No, you should not upgrade the Serverpod CLI tooling version during a project upgrade. Keeping the CLI tooling pinned prevents risky toolchain drift and ensures code generation and migration creation function predictably.

To handle database migrations when updating Serverpod, you must run Serverpod code generation after updating pubspec.yaml entries, then create new migrations. This ensures your database schema matches the newly generated code.

Yes, Serverpod upgrades include specific Docker build constraints. You must verify your installed tooling version and ensure your Docker environment matches the pinned dependency updates to avoid build failures.

Your Serverpod build breaks after updating pubspec.yaml if dependencies are not updated consistently across all packages, or if code generation and migration creation are not run. You must also address any documented breaking changes in models and sessions.