Repository navigation
An in-range update of colors is breaking the build 🚨 #235
Description
The devDependency colors was updated from 1.3.3 to 1.4.0.
This version is covered by your current version range and after updating it in your project the build failed.
colors is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ ci/circleci: Your CircleCI tests were canceled (Details).
Commits
The new version differs by 8 commits.
baa0e1cupdate roadmap56de9f0Add bright/light colors, closes #128b4d964bMake stylize() work for non-ASCI styles (#155)a1407aeDocument colors.enable() and .disable() (#255)acb7f66Merge branch 'develop' of github.com:Marak/colors.js into develop9bfb136more node versions5d9eb90Fixed: throws non-intuitive error on color.red(null) but not on colors.red(undefined) (#261)aa012aaRedo weak equality check so we can colorize null in safe mode (#257)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Activity
greenkeeper commentedon Sep 22, 2019
After pinning to 1.3.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.