Upgrade Scout
Upgrade the dashboard first, then the CLI in each repo. A CLI that gets ahead of the dashboard can have its scans refused until the dashboard catches up.
Upgrade the dashboard
Follow the upgrade steps for how you deployed it:
- with the Helm chart: Deploy the dashboard → Upgrade
- with your own chart: Deploy with your own chart → Upgrade
Upgrade the CLI in a repo
Upgrade @scoutui/cli like any other dev dependency:
npm install --save-dev @scoutui/cli@latest
# or: yarn add -D @scoutui/cli@latest
# or: pnpm add -D @scoutui/cli@latest
Commit the change and merge it into the branch the dashboard tracks.
If the CLI is newer or older than the dashboard
| Message starts with | Fix |
|---|---|
Error: Couldn't upload the scan: this CLI is newer than the dashboard. | Ask whoever runs your dashboard to upgrade it. Until then, run the version the message names, for example npx @scoutui/cli@0.2.4 scan, or install that version in the repo so every upload keeps working. |
Error: Couldn't upload the scan: this CLI is too old for the dashboard. | Upgrade the CLI. Until your upgrade is merged, run the version the message names, for example npx @scoutui/cli@0.2.4 scan. |
scout auth login is refused the same way, with a message that starts Error: Couldn't sign in:. Use the same fixes with auth login in place of scan, for example npx @scoutui/cli@0.2.4 auth login.