The version 15.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 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 ad65c262cf8b1005f5229bc0e4d0a1254f9551a9 on greenkeeper/semantic-release-15.0.0 into 691b52c21ca59e3c75ebe2d218317bbb95d50de0 on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 15.0.0 of semantic-release was just published.
The version 15.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 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.0.015.0.0 (2018-02-19)
Features
prepare
plugin hook (c2beb64)BREAKING CHANGES
publish
plugin hook is not supported anymore and now must be done in theprepare
hookPlugins with a
publish
hook that makes a commit or create a file that can be committed must use theprepare
hook.Commits
The new version differs by 44 commits.
c2beb64
feat: add the
prepare
plugin hook20246c0
fix: exclude empty env var value from replacement
857d418
fix: allow boolean option to be set in config file
4d04901
style: lint
aa724e8
chore(package): simplify xo configuration
ce15b75
chore(package): update xo to version 0.20.0
1966f0e
fix: verify branch first
305f4ee
fix: do not transform repositoryUrl if it allow to push
9788fca
feat: use
@semantic-release/github
as default forsuccess
andfail
hooks04f3061
fix: remove the github plugin from default success and fail hooks
1b3c51d
docs: add missing
success
andfail
options8a2ef48
test: revert to mockserver:latest docker container
ce1e74f
fix: set repository authentication when
repositoryUrl
is set as an optionb6837a2
test: use older version of mockserver
97cb354
feat: improve CLI
There are 44 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: