This repository has been archived by the owner on Jul 10, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 19
chore(deps): update dependency chromatic to v6.19.9 #1700
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/chromatic-6.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
3b76a80
to
c289361
Compare
c289361
to
d1fe45e
Compare
d1fe45e
to
77ee6bd
Compare
77ee6bd
to
4576de2
Compare
4576de2
to
07e337d
Compare
07e337d
to
5c3d513
Compare
5c3d513
to
12d60d6
Compare
12d60d6
to
6124f69
Compare
6124f69
to
7edbc7f
Compare
7514cf6
to
80bc9fd
Compare
80bc9fd
to
edbe294
Compare
edbe294
to
767490b
Compare
767490b
to
6b6e99c
Compare
6b6e99c
to
a390839
Compare
a390839
to
97d711f
Compare
97d711f
to
45bff84
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.7.1
->6.19.9
Release Notes
chromaui/chromatic-cli (chromatic)
v6.19.9
Compare Source
release
event to Github action.v6.19.8
Compare Source
v6.19.7
Compare Source
v6.19.6
Compare Source
isChromatic
exportsv6.19.5
Compare Source
v6.19.4
Compare Source
v6.19.3
Compare Source
v6.19.2
Compare Source
v6.19.1
Compare Source
v6.19.0
Compare Source
v6.18.2
Compare Source
v6.18.1
Compare Source
v6.18.0
Compare Source
v6.17.4
Compare Source
v6.17.3
Compare Source
--only-story-names
flagv6.17.2
Compare Source
v6.17.1
Compare Source
changedFiles
target to fix broken trace utilityv6.17.0
Compare Source
inputs
forworkflow_dispatch
event in GitHub Actionissue_comment
event in GitHub Actionv6.15.0
Compare Source
--repository-slug
flag to CLI, andrepositorySlug
+branchName
options to GitHub Actionv6.14.0
Compare Source
v6.13.1
Compare Source
v6.13.0
Compare Source
v6.12.0
Compare Source
v6.11.4
Compare Source
v6.11.3
Compare Source
v6.11.2
Compare Source
v6.11.1
Compare Source
v6.11.0
Compare Source
v6.10.5
Compare Source
debug
as an option to the GH actionv6.10.4
Compare Source
v6.10.3
Compare Source
v6.10.2
Compare Source
v6.10.1
Compare Source
v6.10.0
Compare Source
--preserve-missing
for--only-story-names
v6.9.0
Compare Source
--only-story-files
flag--untraced
flag validation--force-rebuild
when skipping rebuildv6.8.1
Compare Source
FirstCommittedAtQuery
v6.8.0
Compare Source
--only
to--only-story-names
but keep it as a deprecated alias--preserve-missing
and raise a warning if it's being usedUse 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/orpackage.json
scripts. If you use our GitHub Action, you should remove thepreserveMissing
input (with: ...
) from your workflow config file. Furthermore, you should make sure that yourbuild-storybook
script builds all stories, not just a subset. Check yourstories
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:--only-story-names
to only snapshot stories matching a glob pattern by component/story name.--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
v6.7.3
Compare Source
addon-interactions
to list of supported addonsv6.7.2
Compare Source
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.
This PR has been generated by Mend Renovate. View repository job log here.