The version 15.1.11 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 semantic-release.
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).
Coverage remained the same at 100.0% when pulling 0814f762df022bf48adce98d58bb728b3c45058e on greenkeeper/semantic-release-15.1.11 into c685bd044ac6cde583c44a438ea83ebdf9df90be on master.
Coverage remained the same at 100.0% when pulling c94e9889ad6b3b8c6683d1c874f2a377f968fa73 on greenkeeper/semantic-release-15.1.11 into 78a144ff9d3acbbc6eac86c3b2a7522bb94e1788 on master.
Coverage remained the same at 100.0% when pulling c94e9889ad6b3b8c6683d1c874f2a377f968fa73 on greenkeeper/semantic-release-15.1.11 into 78a144ff9d3acbbc6eac86c3b2a7522bb94e1788 on master.
Version 15.1.11 of semantic-release was just published.
The version 15.1.11 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 semantic-release.
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
v15.1.1115.1.11 (2018-05-01)
Bug Fixes
Commits
The new version differs by 8 commits.
e88ac63
fix: fix Bitbucket authenticated URL
a52f258
refactor: rename
origin
parameters torepositoryUrl
3f61453
test: prevent username/password prompt in
get-git-auth-url
testsd15905c
fix: verify the local branch is up to date with the remote one
a11da0d
docs: fix jsdoc typos
65aaa77
refactor: remove unused test util function
45d7e6f
fix: unshallow repository with credentials
c02b5ca
chore(package): update sinon to version 5.0.1
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: