The version 6.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/git.
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.
commit files from assets even if in they are in .gitignore (629dfc4)
BREAKING CHANGES
the .gitignore file is now ignored when adding files to the release commit
Each files matching a glob in assets will now be included in the release commit. The assets option has now to be configured to match exactly the the files that have to be commited, independently of the .gitignore file.
Commits
The new version differs by 3 commits.
629dfc4feat: commit files from assets even if in they are in .gitignore
fede564chore(package): update sinon to version 6.0.0
3969424chore(package): update nyc to version 12.0.1
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 6.0.0 of @semantic-release/git was just published.
The version 6.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/git.
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
v6.0.06.0.0 (2018-06-27)
Features
assets
even if in they are in.gitignore
(629dfc4)BREAKING CHANGES
.gitignore
file is now ignored when adding files to the release commitEach files matching a glob in
assets
will now be included in the release commit. Theassets
option has now to be configured to match exactly the the files that have to be commited, independently of the.gitignore
file.Commits
The new version differs by 3 commits.
629dfc4
feat: commit files from
assets
even if in they are in.gitignore
fede564
chore(package): update sinon to version 6.0.0
3969424
chore(package): update nyc to version 12.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: