- When you start or restart a project, a Shuttle
deployerDocker container is started with the latest released version of Shuttle.
- When you deploy something to that project, the version of your
shuttle-...cargo dependencies are recommended to be of the same version of
deployer, as there might be breaking changes between releases.
- It is also recommended to keep
cargo-shuttleup to date with the current version of the Shuttle API (see latest release).
Upgrading Shuttle version
Combining all of the above, these are the recommended steps for upgrading a Shuttle app.
cargo install cargo-shuttle, or if you’re using cargo-binstall,
cargo binstall cargo-shuttle.
Update your project’s
shuttle-runtime = "0.27.0" # etc
Test that your project works with
cargo shuttle run.
Upgrade your project container with
cargo shuttle project restart. (Remember to use
--idle-minutesif relevant.) This will not delete any databases, and you will keep your project name.
Finally, redeploy your Shuttle app:
cargo shuttle deploy. (if you want to, commit your changes first)