Shuttle: v0.23.0 update
We're excited to release shuttle v0.23.0! 🚀
Bug fixes
- Fixed a bug where the shuttle-next runtime binary was not being installed in the project container image, leading to failing deploys of shuttle-next projects.
- Fixed a bug where MongoDB shared database data was not persisted between project restarts.
Contributions
- @d4ckard added a check for if the cargo-shuttle CLI and the shuttle-runtime versions are out of sync in #1088
- @skaunov updated an example in our docs in shuttle-hq/shuttle-docs#159
Upgrading
To upgrade your shuttle CLI, run: cargo install cargo-shuttle, or if you’re using [cargo-binstall](https://github.com/cargo-bins/cargo-binstall), cargo binstall cargo-shuttle.
If you’d like to upgrade your project container, run the restart project command. This will not delete any databases, and you will keep your project name:
cargo shuttle project restartFinally, redeploy your shuttle service:
cargo shuttle deploy
Commits for this release
- fix: add volume to mongo container by @oddgrd in #1126
- feat: gateway to start last deploy from idle project by @chesedo in #1121
- fix: install shuttle-next runtime in deployers by @oddgrd in #1127
- misc: add warning for api url arg by @jonaro00 in #1128
- ci: separate jobs for faster ci verdict by @jonaro00 in #1130
- docs: update readme, separate contributing and development docs by @jonaro00 in #1124
- feat(runtime): add alpha runtime version check by @d4ckard in #1088
- deployer: sync resource-recorder with persistence by @iulianbarbu in #1101
- chore: v0.23.0 by @oddgrd in #1133
New Contributors
Full Changelog: v0.22.0...v0.23.0