You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 CircleCI is running your tests Details
Version 3.2.0 of cross-env just got published.
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 CircleCI is running your tests Details
❌ continuous-integration/appveyor/branch AppVeyor build failed 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 🌴
The text was updated successfully, but these errors were encountered: