An in-range update of cross-env is breaking the build π¨
greenkeeper opened this issue Β· comments
Version 3.2.0 of cross-env just got published.
Branch | Build failing π¨ |
---|---|
Dependency | cross-env |
Current Version | 3.1.4 |
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
- β ci/circleci Your tests failed on CircleCI Details
Release Notes
v3.2.0<a name"3.2.0">
3.2.0 (2017-03-04)
Features
Commits
The new version differs by 4 commits .
dad00c4
feat(revamp): revamp the entire lib (backward compatible) (#63)
e33a85c
docs(README): Add doc for cross-var. (#58)
5e590ec
docs(README): added how to use cross-env to run npm sub-scripts (#53)
afdb2de
docs(README): mention Bash on Windows (#49)
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 3.2.1 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Version 3.2.2 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Version 3.2.3 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Release Notes
v3.2.3<a name"3.2.3">