The version 0.12.0 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of osprey-method-handler.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release NotesUpdated dependencies
Updated dependencies.
Fixes
Issue validating against !included JSON schemas in types#29
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).
Coverage remained the same at 96.07% when pulling 05257882bb9a9f0c7b8c0e340e6d844e7eed8368 on greenkeeper/osprey-method-handler-0.12.0 into c7ddbc7606c5cb0af6a44f4e710fa19c9899a8e5 on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 0.12.0 of osprey-method-handler was just published.
The version 0.12.0 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of osprey-method-handler.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
Updated dependenciesUpdated dependencies.
Fixes
!include
d JSON schemas intypes
#29Commits
The new version differs by 15 commits.
448ecec
0.12.0
1546dc0
updated dependencies
2dda6ba
updating travis file
84d1d1f
adding package lock file
1f9729e
Merge pull request #33 from mulesoft-labs/greenkeeper/initial
44e67c3
Merge branch 'master' into greenkeeper/initial
930d0fe
Merge pull request #32 from ForsakenHarmony/update
424681d
Merge pull request #31 from ForsakenHarmony/master
3a561a1
upgrade ajv to 6.4.0
e54e9db
downgrade ajv to 4.7.0. update for standard 11.0.0
ae5aef4
docs(readme): add Greenkeeper badge
0d7e34e
chore(package): update dependencies
e2d12e8
Update package versions
fcab36a
Update .travis.yml to current LTS
8bb2680
Check for JSON schemas properly (fixes #29)
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: