An in-range update of ajv is breaking the build π¨
greenkeeper opened this issue Β· comments
Version 5.1.6 of ajv just got published.
Branch | Build failing π¨ |
---|---|
Dependency | ajv |
Current Version | 5.1.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As ajv 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 8 commits.
ff9f93a
5.1.6
0d6ae42
fix: traverse only schema objects, fixes #521
daf7d6b
docs: using with draft-04
9f0b563
Merge pull request #508 from epoberezkin/greenkeeper/nyc-11.0.2
55727d9
test: remove node v0.12, v5, add v8 to travis test
eac5902
chore(package): update nyc to version 11.0.2
f1c9f15
Merge pull request #507 from epoberezkin/greenkeeper/chai-4.0.1
d74a381
chore(package): update chai to version 4.0.1
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 π΄
After pinning to 5.1.5 your tests are passing again. Downgrade this dependency π.
Version 5.2.0 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Release Notes
5.2.0Refactor: separate "equal" into package fast-deep-equal