Skip to content
Discussion options

You must be logged in to vote

We bumped to 4.2.0 with #20230. The yarn.lock was pinned to 4.1.0 so there should not have been an impacted version of tinycolor in the supply chain as far as I know.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by kburtram
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants