Closed greenkeeper[bot] closed 6 years ago
After pinning to 1.18.12 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
Version 1.19.0 of urijs just got published.
This version is covered by your current version range and after updating it in your project the build failed.
urijs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ✅ **ci/circleci** Your tests passed on CircleCI! [Details](https://circleci.com/gh/hairyhenderson/passport-fellowshipone/225?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/hairyhenderson/passport-fellowshipone/builds/281909857?utm_source=github_status&utm_medium=notification)Release Notes
1.19.0 (October 1st 2017).setFragment()
to query fragment plugin - Issue #338, PR #356URI.preventInvalidHostname
to control if an error should be thrown on invalid input - Issue #352, Issue #354, Issue #355 - effectively making the changes of version 1.18.11 opt-in rather than default.Commits
The new version differs by 4 commits.
fde82ec
chore(build): bumping to version 1.19.0
3cc5c22
chore(build): bumping to version 1.19.0
d1cedf2
fix(parse): add URI.preventInvalidHostname to make hostname validation optional - #345, 352, #354, #355
29ab103
feature(fragment-query): add setFragment()
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: