The version 4.1.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).
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 4.1.0 of swagger-parser was just published.
The version 4.1.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 105 commits.
07575d7release v4.1.047d1baaupdated dependencies5c5eea6RemovedArray.find()from test code, since it isn't supported by IEe87a254re-generated the github-pages contentbbf1c79either run the Mocha (Node.js) tests OR the Karma (web browser) tests on each CI instance, not bothe62c75fsome of the "real world" APIs fail validation on web browsers (other than Chrome) due to unsupported RegExp syntax72398edremoved some "known API errors" that are no longer valid1b73447Merge branch 'marcelstoer-master'e92ad70fixed a typof7b55d0Merge branch 'master' of https://github.com/marcelstoer/swagger-parser into marcelstoer-master20f7cfcmodified test fixtures to use karma-host-environment, so they work in Node and browsers88badf8added karma-host-environment to simplify testing across Node and browsers6ba7a1agive up after 3 retries, rather than throwing an error2bcbdadfixed a bug in the retry logicfad3d45added retry logic to the "real world" tests, to handle download failuresThere are 105 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: