Chromatic suddenly started failing claiming we have an older version of storybook, but in fact do not.

We have a typescript monorepo which has a design system that’s been happily building with chromatic for review nicely.

today it suddenly started failing:

Please note the session id: 'REDACTED'
contact [[e-mail]](mailto:[e-mail]) -or- open a support ticket at https://www.chromatic.com/
 
chromatic ERR! Problems encountered: 
chromatic ERR! Chromatic requires Storybook version at least 3.4. Please update your Storybook! 
 
undefined
/opt/atlassian/pipelines/agent/build/design-system/storybook:
 ERROR  @****/balance-storybook@1.0.34 chromatic: `chromatic --project-token=$CHROMATIC_PROJECT_TOKEN --exit-zero-on-changes`
Exit status 255
 ERROR  Command failed with exit code 1.

in that .../design-system/storybook/package.json#dependencies :

...

     "chromatic": "^4.0.2",
  },
  "devDependencies": {
    "@babel/core": "^7.9.6",
    "@storybook/addon-actions": "^6.2.9",
    "@storybook/addon-knobs": "6.2.9",
    "@storybook/addon-links": "^6.2.9",
    "@storybook/addon-storysource": "^5.3.18",
    "@storybook/addons": "6.2.9",
    "@storybook/react": "^6.2.9",
    "babel-loader": "^8.2.2"
  }
...

[ghengeveld]

This issue usually pops up when running an outdated version of the CLI. Please make sure you have installed the latest version of chromatic:

Additionally, make sure that you are not using storybook-chromatic, which is an ancient version of the CLI which is no longer supported. If you have it installed, please remove it. Don’t forget to check your lockfile.

If you want to automatically upgrade to the latest version of chromatic going forward, you can remove the dependency altogether and use npx when running it (npx chromatic ...). Or you can use our GitHub Action.

[DzmitrySiniakou]

I have the same issue