The version 4.0.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 swagger-parser.
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.
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).
Version 4.0.0 of swagger-parser was just published.
The version 4.0.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 swagger-parser.
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.
Commits
The new version differs by 61 commits.
3689c62release v4.0.06928836updated dependencies6913678Changelog for v4.0.0 (final)0f07f42Updated the website to support new options9e38fb2moved some website files aroundde6fc8aupdated buildf8986afset lenient tolerances in CI, due to flaky browser behavior1f4a644Fixed typos148d5c1Removed headless Firefox from the CI tests, since it keeps dropping its connection to Karma, causing the build to fail4c02007Skip the bungie.net API in tests for now (BigstickCarpet/json-schema-ref-parser#56)f5637dcMerge branch 'master' of https://github.com/BigstickCarpet/swagger-parser67b1dd6Merge pull request #57 from ashish1729/patch-17615441apis.guru now has over 600 APIs!becd962fixed the "npm run karma" script for local developmentf68d135refactored some tests to match the new behavior of JSON Schema $Ref ParserThere are 61 commits in total.
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: