Migration guide
Upgrading to v5
CLI 5 brings config schema 5, a single token variable and new dashboard shortcuts. Most projects upgrade in under ten minutes; the steps below are in the order we recommend.
- CLI5.0.2
- Config schema5
- Node.js≥ 20
- ReleasedOct 8, 2026
01Update the CLI
Terminal $ npm install -g @rivetlane/cli@5$ rivet --versionrivet/5.0.2 darwin-arm64 node-v20.17.002Migrate rivetlane.toml
rivet migrate configrewrites the file to schema 5: it addsschema = 5and renamesbuild.publishtobuild.output. Comments and ordering are kept.Terminal $ rivet migrate config --dry-run~ build.publish → build.output+ schema = 5$ rivet migrate config✓ Migrated rivetlane.toml to schema 503Rename the token variable
Replace
RIVET_API_KEYwithRIVET_TOKENin every CI provider and secret store. The value does not change.04Review env pull before you run it
rivet env pullnow writes exactly what thedevelopmentscope contains, so local runs match deploys.
Dashboard shortcuts
The v5 dashboard adds two-key navigation. Press ? anywhere to see this list.
| Action | Shortcut |
|---|---|
| Open the command menu | ⌘K |
| Go to deploymentsNew | GthenD |
| Go to previewsNew | GthenP |
| Redeploy the current deploymentChanged | ⇧R |
| Stream logsNew | L |
| Show all shortcuts | ? |