search

wuespace / telestion-client

Telestion Frontend Framework (Technical leads: Ludwig Richter, Jan Tischhöfer)
https://telestion.wuespace.de
MIT License
7 stars 1 forks source link

chore(deps-dev): bump chromatic from 6.5.1 to 6.10.0 #1526

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps chromatic from 6.5.1 to 6.10.0.

Changelog

Sourced from chromatic's changelog.

6.10.0 - 2022-09-23

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

6.9.0 - 2022-09-02

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

6.8.1 - 2022-09-01

  • 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

6.8.0 - 2022-08-26

  • 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.

6.7.4 - 2022-08-11

  • 624 Read Webpack stats file as stream to support very large projects

6.7.3 - 2022-08-01

  • 621 Add addon-interactions to list of supported addons

6.7.2 - 2022-07-28

  • 615 Changed trim stats to stream and added test

... (truncated)

Commits
  • eea9ad8 6.10.0
  • dd52e5c 6.10.0
  • f80a118 Merge pull request #643 from chromaui/ghengeveld/ap-2404-fix-implied-preserve...
  • 186607e Merge branch 'main' into ghengeveld/ap-2404-fix-implied-preservemissing-for
  • 65b33f7 Fix implied --preserve-missing for --only-story-names
  • 2371b81 Merge pull request #620 from SiTaggart/feat/add-changecount
  • 9ce5439 Merge branch 'main' into feat/add-changecount
  • c69ebd1 6.9.0
  • 8c7f4da 6.9.0
  • 6ac6cbc Merge pull request #634 from chromaui/ghengeveld/ap-2275-add---only-story-fil...
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

Superseded by #1537.