"Invalid --untraced" error

[rburkovsky]

Started getting this:

Run chromaui/action@v1

Chromatic CLI v6.3.0
https://www.chromatic.com/docs/cli

✖ Invalid --untraced
This option can only be used in conjunction with --only-changed
→ View the full stacktrace below

If you need help, please chat with us at https://www.chromatic.com/docs/cli for the fastest response.
You can also email the team at [email protected] if chat is not an option.

Please provide us with the above CLI output and the following info:
{
  "timestamp": "2021-12-22T12:19:49.677Z",
  "sessionId": "28c105e1-cd45-4fb4-8bfe-0743016c2920",
  "nodePlatform": "linux",
  "nodeVersion": "12.13.1",
  "packageName": "chromatic",
  "packageVersion": "6.3.0",
  "flags": {
    "projectToken": "***",
    "fromCI": true,
    "interactive": false,
    "exitZeroOnChanges": true,
    "exitOnceUploaded": false,
    "allowConsoleErrors": false
  },
  "errorType": "Error",
  "errorMessage": "✖ Invalid --untraced"
}

Error: ✖ Invalid --untraced
This option can only be used in conjunction with --only-changed
    at /home/runner/work/_actions/chromaui/action/v1/action/main.js:285:517
    at yn (/home/runner/work/_actions/chromaui/action/v1/action/main.js:314:268)
    at gn (/home/runner/work/_actions/chromaui/action/v1/action/main.js:244:246)
    at /home/runner/work/_actions/chromaui/action/v1/action/main.js:350:1609690
    at /home/runner/work/_actions/chromaui/action/v1/action/main.js:350:1608861
    at Object.next (/home/runner/work/_actions/chromaui/action/v1/action/main.js:350:1608966)
    at o (/home/runner/work/_actions/chromaui/action/v1/action/main.js:350:1607680)
Could not retrieve package info from registry; skipping update check

in workflow.yml:

      - name: Publish to Chromatic
        if: github.ref != 'refs/heads/main'
        uses: chromaui/action@v1
        # Required options for the Chromatic GitHub Action
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          # 👇 Chromatic projectToken, refer to the manage page to obtain it.
          projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
        # 👇 Checks if the branch is main and accepts all changes in Chromatic
      - name: Publish to Chromatic and auto accept changes
        if: github.ref == 'refs/heads/main'
        uses: chromaui/action@v1
        # Required options for the Chromatic GitHub Action
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          # 👇 Chromatic projectToken, refer to the manage page to obtain it.
          projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
          autoAcceptChanges: true # 👈 Option to accept all changes

[rburkovsky]

Tried adding onlyChanged: true option in workflow, but then it started giving me

✖ Failed to retrieve git information
Expected pattern to be a non-empty string
→ View the full stacktrace below

If you need help, please chat with us at https://www.chromatic.com/docs/cli for the fastest response.
You can also email the team at [email protected] if chat is not an option.

Please provide us with the above CLI output and the following info:
{
  "timestamp": "2021-12-22T12:29:43.904Z",
  "sessionId": "110ae7f8-1d61-4687-a5ed-f82aeab9439d",
  "gitVersion": "2.34.1",
  "nodePlatform": "linux",
  "nodeVersion": "12.13.1",
  "packageName": "chromatic",
  "packageVersion": "6.3.0",
  "flags": {
    "projectToken": "***",
    "onlyChanged": true,
    "fromCI": true,
    "interactive": false,
    "exitZeroOnChanges": true,
    "exitOnceUploaded": false,
    "allowConsoleErrors": false
  },
  "buildScript": "npx build-storybook -s public",
  "errorType": "TypeError",
  "errorMessage": "✖ Failed to retrieve git information",
  "build": {
    "number": 431,
    "webUrl": "https://www.chromatic.com/build?appId=6154db2eb7cd94003aefe923&number=431"
  }
}

[banditlev]

Having the same problem. Seems to be an issue with the latest release 6.3.0 👉 https://github.com/chromaui/chromatic-cli/runs/4606379156?check_suite_focus=true

[Twixes]

Seeing the same thing too.

[MikhailYahorau]

Same issue

[andresmalves]

Same issue too

[oleksify]

Same issue here. No way around it for now :(

[yannbf]

Hey everyone, thanks for opening this issue. We're currently working on that and will try to release a fix as soon as possible!
We appreciate your patience 🙏

[yannbf]

Is anyone running the chromatic command directly and not via the github action?

[riccardo-forina]

From the cli it works fine

[yannbf]

From the cli it works fine

Thank you so much! That helps a ton. We are currently releasing another version that should not throw that error anymore. Will be up in a few moments!

[yannbf]

Hey everyone, version 6.3.2 has been released and should address this issue.

[riccardo-forina]

I can confirm builds are passing again. Thanks!