chore(deps): update dependency chromatic to v6.10.5

v6.10.5

Compare Source

• 661 Add debug as an option to the GH action

v6.10.4

Compare Source

v6.10.3

Compare Source

• 651 Update buildHasErrors with interaction test failure specific messaging

v6.10.2

Compare Source

• 649 Fix TurboSnap for module names containing URL params in stats file
• 650 Ensure all GitHub Action outputs are exposed

v6.10.1

Compare Source

• 645 Check onlyStoryNames is non-empty

v6.10.0

Compare Source

• 620 Add various counts as GitHub Action outputs
• 643 Fix implied --preserve-missing for --only-story-names

v6.9.0

Compare Source

• 634 Add --only-story-files flag
• 565 Add tests for --untraced flag validation
• 636 Suggest using --force-rebuild when skipping rebuild

v6.8.1

Compare Source

• 635 Retry queries by default and allow even more retries for FirstCommittedAtQuery
• 607 Bump terser from 4.8.0 to 4.8.1
• 601 Bump moment from 2.29.1 to 2.29.4
• 594 Bump shell-quote from 1.7.2 to 1.7.3
• 553 Bump minimist from 1.2.5 to 1.2.6
• 631 Bump @​actions/core from 1.5.0 to 1.9.1

v6.8.0

Compare Source

• 630 Rename --only to --only-story-names but keep it as a deprecated alias
• 629 Deprecate --preserve-missing and raise a warning if it's being used

Use TurboSnap instead of preserveMissing

In order to support advanced use cases where only a subset of stories would be included in a Storybook, the --preserve-missing flag could be used to prevent excluded stories from being marked as "removed" in Chromatic. This behavior could lead to problematic situations regarding infrastructure upgrades and cause truly removed stories to never be removed from Chromatic. That's why we are sunsetting the "preserve missing" behavior. As of v6.8.0, using this flag will raise a warning message in the CLI. In a future major version, the flag will be removed completely, and continuing to use it with an older CLI version will start to fail your build.

To upgrade, you should remove the --preserve-missing flag from your CI and/or package.json scripts. If you use our GitHub Action, you should remove the preserveMissing input (with: ...) from your workflow config file. Furthermore, you should make sure that your build-storybook script builds all stories, not just a subset. Check your stories configuration in .storybook/main.js so it doesn't omit any stories (e.g. based on an environment variable).

Most likely you were using preserveMissing to cut down on the number of snapshots taken by Chromatic. To achieve the same goal, you have three options:

• Recommended: Use TurboSnap to automatically only snapshot stories for which related source files have changed.
• Use --only-story-names to only snapshot stories matching a glob pattern by component/story name.
• (Soon) Use --only-story-files to only snapshot stories matching a glob pattern by story filename.

In each of these cases, any stories that aren't captured are "inherited" from their baseline.