Version 2.0.20 of browser-env just got published.
|
Branch
|
Build failing 🚨
|
|
Dependency
|
browser-env
|
|
Current Version
|
2.0.19
|
|
Type
|
devDependency
|
This version is covered by your current version range and after updating it in your project the build failed.
As browser-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
- ❌ dependency-ci Failed dependency checks Details
Commits
The new version differs by 4 commits .
3e5e9b9 2.0.20ac13707 fix(package): update jsdom to version 9.10.0 (#32)8569dd3 chore(package): update ava to version 0.18.0a36ec73 Change npm badge to show monthly downloads
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 2.0.20 of browser-env just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As browser-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
Commits
The new version differs by 4 commits .
3e5e9b92.0.20ac13707fix(package): update jsdom to version 9.10.0 (#32)8569dd3chore(package): update ava to version 0.18.0a36ec73Change npm badge to show monthly downloadsSee 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 🌴