fix: add cupid to progress styles#7076
Conversation
There was a problem hiding this comment.
I don't know that this needs it's own version but happy to discuss further.
There was a problem hiding this comment.
StreamReport is widely used so it is relatively difficult to determine. Try using your IDE to determine which workspaces import StreamReport in their source code (not test code) to see which ones to needs to release.
There was a problem hiding this comment.
Thanks @clemyan! I was able to figure out how to determine the packages that would need to be bumped.
What I was unsure of is if this is a change that would actually warrant its own release be created for those packages or should just be part of a future release. If you have any guidance on that question of “if” I’m happy to update the PR. Thanks again for reviewing.
There was a problem hiding this comment.
What I was unsure of is if this is a change that would actually warrant its own release
Sounds like you are confused about our release process? Each PR (including this) should record which packages need releases for the change to be effective. Then when it is time to cut a release, we aggregate all the stored records to decide which packages to release and with what version. You can run yarn version check -i to create that record interactively.
2 participants
What's the problem this PR addresses?
Addresses lack of whimsy on February 14th.
How did you fix it?
Added cupid.
Checklist