chromatic-cli: New storybook v6.4.22 version is failing in Github Action env

Tried to upgrade to v6.4.22 and suddenly the CI environment in Github Actions started breaking.

The versions that were bumped from -> to

    "@storybook/addon-a11y": "^6.4.19",
    "@storybook/addon-actions": "^6.3.12",
    "@storybook/addon-essentials": "^6.3.12",
    "@storybook/addon-links": "^6.3.12",
    "@storybook/addon-storysource": "^6.4.19",
    "@storybook/react": "^6.3.12",

    "@storybook/addon-a11y": "^6.4.22",
    "@storybook/addon-actions": "^6.4.22",
    "@storybook/addon-essentials": "^6.4.22",
    "@storybook/addon-links": "^6.4.22",
    "@storybook/addon-storysource": "^6.4.22",
    "@storybook/react": "^6.4.22",

And the issue appeared when the npm run command was executed every time. When I reverted back the yarn.lock file everything worked again.

The debug logs from the Github action is also attached in case you find it helpful

visual-testing-logs.txt

About this issue

Original URL
State: open
Created 2 years ago
Comments: 15 (7 by maintainers)

Most upvoted comments

@iamswain25 I’d advise writing in to Chromatic support with some details and we can help you out further.

tmeasday on Jul 28, 2022

Not sure @tmeasday , the issue I can see as all packages are using the latest version: issue

When I manually added the '@storybook/addon-actions' in main.js the build completed but with some issues (no stories at all inside)

Chromatic CLI v6.6.3
https://www.chromatic.com/docs/cli
Authenticating with Chromatic
    → Connecting to https://index.chromatic.com
Authenticated with Chromatic
    → Using project token '********8166'
Retrieving git information
Retrieved git information
    → Commit '4468b41' on branch 'dropdown'; found 1 parent build
Collecting Storybook metadata
Collected Storybook metadata
    → ; no supported addons found
Initializing build
Initialized build
    → Build 136 initialized
Building your Storybook
    → Running command: npm run --silent build-storybook -- --output-dir /tmp/chromatic--1[9](https://github.com/neo4j/neo4j-design/runs/6968909713?check_suite_focus=true#step:5:10)06-9J9A[13](https://github.com/neo4j/neo4j-design/runs/6968909713?check_suite_focus=true#step:5:14)klZtPY
Storybook built in 41 seconds
    → View build log at /home/runner/work/neo4j-design/neo4j-design/packages/react-storybook/build-storybook.log
Publish your built Storybook
    → Validating Storybook files
Publishing your built Storybook
    → Retrieving target location
    → Starting publish
Publish complete in 5 seconds
    → View your Storybook at https://6[22](https://github.com/neo4j/neo4j-design/runs/6968909713?check_suite_focus=true#step:5:23)5e0c9734f0d003a2cf577-migvsbrnke.chromatic.com
Verifying your Storybook
    → This may take a few minutes
✖ Failed to extract stories from your Storybook
This is usually a problem with your published Storybook, not with Chromatic.
Build and open your Storybook locally and check the browser console for errors.
Visit your published Storybook at https://62[25](https://github.com/neo4j/neo4j-design/runs/6968909713?check_suite_focus=true#step:5:26)e0c97[34](https://github.com/neo4j/neo4j-design/runs/6968909713?check_suite_focus=true#step:5:35)f0d003a2cf577-migvsbrnke.chromatic.com
The following error was encountered while running your Storybook:
    → Failed to publish build

I would make an educated guess, that the issue is coming from the npm run rather than choosing yarn as locally it builds fine with the yarn build

konsalex on Jun 20, 2022