-
Notifications
You must be signed in to change notification settings - Fork 391
fix: pin colors to 1.4.0 #3995
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
fix: pin colors to 1.4.0 #3995
Conversation
📊 Benchmark resultsComparing with 443cc60 Package size: 356 MB⬆️ 0.00% increase vs. 443cc60
Legend
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I don't think this PR fixes the issue... Since this project is using a lock file, this add a redundant dependency which does not enforce the package managers to respect it in any way. One solution would be to use The best solution would be to bug the direct parents of |
This is a not ideal solution for
Those work at the consumer level, and not at the publisher level as far as I know (overrides is quite new as well and only supported in latest
💯 And we'll follow up with that. |
But this change here does not do this. You can try it and you'll see that whatever you have in the root project as a dependency, is ignored downlevel. |
Oh well, maybe because I didn't really pin it. Testing #3998 |
@erezrokah I think you can update to the latest prettyjson which has colors now pinned too. |
🎉 Thanks for submitting a pull request! 🎉
Summary
Fixes #3981
We don't use colors as a direct dependency, however by installing it as one, we can force package managers to use the unbroken version.
For us to review and ship your PR efficiently, please perform the following steps:
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)
🐒