Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency chromatic to v6.24.1 - autoclosed #522

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 30, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
chromatic (source) 6.6.4 -> 6.24.1 age adoption passing confidence

Release Notes

chromaui/chromatic-cli (chromatic)

v6.24.1

Compare Source

  • 803 Support Mode Name as Suffix for Build Progress Indicator

v6.24.0

Compare Source

  • 801 Fix Unexpected build status: PREPARED error
  • 802 Include all commit info in GitInfo

v6.23.1

Compare Source

  • 800 Fix type signature for runAll and runBuild

v6.23.0

Compare Source

  • 795 Add --local flag and pass to builds as isLocalBuild
  • 796 Pass gitUserEmailHash up with new builds and use localBuilds filter in baseline calculations

v6.22.0

Compare Source

  • 798 Calculate and record uncommittedHash when creating a build

v6.21.0

Compare Source

  • 794 Add getGitInfo function exported by the Node API
  • 780 Add support for schedule GitHub Action workflow trigger
  • 793 Update snyk parser and added tests for yarn berry

v6.20.0

Compare Source

  • 788 Track Build ID for Storybook Uploads

v6.19.9

Compare Source

  • 734 Add support for release event to Github action.
  • 750 Update CI to store tokens in environment variables
  • 775 Increase timeout for Git command(s) execution

v6.19.8

Compare Source

  • 765 Add some fields to package.json to help resolve types in entrypoints
  • 773 Bump the Loggly Dependency

v6.19.7

Compare Source

  • 770 Ensure we exit with a code at the end

v6.19.6

Compare Source

  • 768 Add isChromatic exports

v6.19.5

Compare Source

  • 763 Fix issue with onTaskComplete callback

v6.19.4

Compare Source

  • 764 Move all depenendencies to dev deps

v6.19.3

Compare Source

v6.19.2

Compare Source

  • 756 Added onTaskComplete callback option
  • 755 Add a node entry point

v6.19.1

Compare Source

v6.19.0

Compare Source

v6.18.2

Compare Source

  • 758 Add additional logging for turbosnap
  • 753 Update getStorybookMetadata to safely record version even if fails to parse mainConfig

v6.18.1

Compare Source

v6.18.0

Compare Source

  • 737 Better discovery for TurboSnap trace-changed and related directories
  • 747 Fix Storybook config detection by adding serverRequire to interpret files

v6.17.4

Compare Source

  • 738 Get the builder name and version via the mainConfig for SB v7+
  • 743 Bump Snyk lockfile parser dependency

v6.17.3

Compare Source

  • 730 Disconnect preserveMissing from --only-story-names flag

v6.17.2

Compare Source

  • 726 Increase timeout on Storybook Verification
  • 725 Bump webpack from 5.72.1 to 5.76.0
  • 711 Bump http-cache-semantics from 4.1.0 to 4.1.1

v6.17.1

Compare Source

  • 718 Update changedFiles target to fix broken trace utility

v6.17.0

Compare Source

  • 695 Omit inputs for workflow_dispatch event in GitHub Action
  • 713 Add support for issue_comment event in GitHub Action

v6.15.0

Compare Source

  • 710 Add --repository-slug flag to CLI, and repositorySlug + branchName options to GitHub Action

v6.14.0

Compare Source

  • 683 Enhanced TurboSnap: Trace dependency changes instead of bailing out
  • 694 Remove tunnel flags

v6.13.1

Compare Source

  • 700 Revert "Don't bundle package.json but rely on meow's runtime value instead"

v6.13.0

Compare Source

  • 676 Log message when TurboSnap is unavailable
  • 671 Don't bundle package.json but rely on meow's runtime value instead
  • 675 Output progress updates in non-interactive mode every 10 seconds

v6.12.0

Compare Source

  • 685 Support custom DNS IP and DNS failover IP using custom DNS resolver
  • 689 Improve the failure message when there's only one git commit

v6.11.4

Compare Source

v6.11.3

Compare Source

  • 670 Trace command errors for package manifest change
  • 659 Add interactionTestFailuresCount to GitHub Action output
  • 660 Update GitHub Action to Node 16
  • 644 Bump node-fetch from 3.0.0 to 3.2.10
  • 666 Bump @​actions/core from ^1.5.0 to ^1.10.0

v6.11.2

Compare Source

  • 667 Edit package file detection process for the untraced flag

v6.11.1

Compare Source

  • 665 Added onlyStoryFiles to the github action

v6.11.0

Compare Source

  • 648 TurboSnap not bailed if package manifest change isn't dependency-related

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.

v6.7.4

Compare Source

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

v6.7.3

Compare Source

  • 621 Add addon-interactions to list of supported addons

v6.7.2

Compare Source

  • 615 Changed trim stats to stream and added test

v6.7.1

Compare Source

  • 612 Add change count to buildPassed message if changes exist

v6.7.0

Compare Source

  • 598 Enable bash mode for globs when matching branches with picomatch

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Jun 30, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
webdev-template ❌ Failed (Inspect) Dec 16, 2023 4:33pm

@codecov
Copy link

codecov bot commented Jun 30, 2022

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (da39ee0) 100.00% compared to head (6b140e6) 100.00%.
Report is 1 commits behind head on main.

❗ Current head 6b140e6 differs from pull request most recent head 36e4690. Consider uploading reports for the commit 36e4690 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #522   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           76        76           
  Branches         5         5           
=========================================
  Hits            76        76           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot changed the title Update dependency chromatic to v6.7.0 Update dependency chromatic to v6.7.1 Jul 22, 2022
@renovate renovate bot changed the title Update dependency chromatic to v6.7.1 Update dependency chromatic to v6.7.2 Jul 28, 2022
@renovate renovate bot changed the title Update dependency chromatic to v6.7.2 Update dependency chromatic to v6.7.3 Aug 1, 2022
@renovate renovate bot changed the title Update dependency chromatic to v6.7.3 Update dependency chromatic to v6.7.4 Aug 11, 2022
@renovate renovate bot changed the title Update dependency chromatic to v6.7.4 Update dependency chromatic to v6.8.0 Aug 26, 2022
@renovate renovate bot changed the title Update dependency chromatic to v6.8.0 Update dependency chromatic to v6.10.0 Sep 25, 2022
@renovate renovate bot changed the title Update dependency chromatic to v6.10.0 Update dependency chromatic to v6.11.4 Nov 20, 2022
@renovate renovate bot changed the title Update dependency chromatic to v6.11.4 Update dependency chromatic to v6.17.1 Mar 16, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.17.1 Update dependency chromatic to v6.17.2 Mar 21, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.19.9 Update dependency chromatic to v6.20.0 Jul 21, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.20.0 Update dependency chromatic to v6.21.0 Aug 7, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.21.0 Update dependency chromatic to v6.22.0 Aug 15, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.22.0 Update dependency chromatic to v6.23.0 Aug 22, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.23.0 Update dependency chromatic to v6.23.1 Aug 24, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.23.1 Update dependency chromatic to v6.24.0 Aug 24, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.24.0 Update dependency chromatic to v6.24.1 Aug 25, 2023
@renovate renovate bot changed the title Update dependency chromatic to v6.24.1 Update dependency chromatic to v6.24.1 - autoclosed Dec 16, 2023
@renovate renovate bot closed this Dec 16, 2023
@renovate renovate bot deleted the renovate/chromatic-6.x branch December 16, 2023 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants