An in-range update of cross-env is breaking the build π¨
greenkeeper opened this issue Β· comments
Version 5.0.1 of cross-env just got published.
Branch | Build failing π¨ |
---|---|
Dependency | cross-env |
Current Version | 5.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As cross-env is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
Release Notes
v5.0.1<a name"5.0.1">
5.0.1 (2017-06-08)
Bug Fixes
Commits
The new version differs by 2 commits.
b10de51
fix: Change splitter regex to use .* instead of .+ (#117)
c9908f3
test(JSON): add JSON value tests that work on both Windows and UNIX (#112)
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Version 5.0.2 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
v5.0.2<a name"5.0.2">
5.0.2 (2017-08-01)
Bug Fixes
Version 5.0.3 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
v5.0.3<a name"5.0.3">
5.0.3 (2017-08-03)
Bug Fixes
Version 5.0.4 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
v5.0.4<a name"5.0.4">
5.0.4 (2017-08-06)
Bug Fixes
Version 5.0.5 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
v5.0.5<a name"5.0.5">
5.0.5 (2017-08-08)
Bug Fixes
- docs: add malware warning to README (44b37dd1)