This version is covered by your current version range and after updating it in your project the build failed.
validate-fptf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/juliuste/train-ose/builds/500793391?utm_source=github_status&utm_medium=notification)).
Commits
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
After pinning to 2.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
The devDependency validate-fptf was updated from
2.1.1
to2.2.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
validate-fptf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/juliuste/train-ose/builds/500793391?utm_source=github_status&utm_medium=notification)).Commits
The new version differs by 3 commits.
49a192d
FPTF 1.2.1, 2.2.0
1a13ffd
validate journeyLeg.price
da4221e
drop URL-safety requirements for IDs
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: