The version 12.2.2 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 94.554% when pulling 5e82da05b58537389aa0cfae714d2bbea771e5ab on greenkeeper/semantic-release-12.2.2 into 9ce761b09a7c5ef9d8011a94a8c159ef9e690c44 on master.
Coverage remained the same at 94.554% when pulling 1773e94dd0af0a01cb5d800e768b55a31c961f3d on greenkeeper/semantic-release-12.2.2 into 9ce761b09a7c5ef9d8011a94a8c159ef9e690c44 on master.
Update semantic-release to the latest version 🚀
(a dependency was not added, add to revert master)
Original PR is #266
Version 12.2.2 of semantic-release was just published.
The version 12.2.2 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
v12.2.212.2.2 (2018-01-13)
Bug Fixes
Commits
The new version differs by 21 commits.
cc0c312
fix: set node minimum version to 8.3
93173e2
fix(package): update execa to version 0.9.0
48ade92
chore(package): update prettier to version 1.10.0
49ad198
docs(contrib): add atomic commits requirement
adbcca6
docs: add issue template
e0b4e6a
docs: add CONTRIBUTING guidelines
53f3de6
feat: allow to exclude commits from analysis
fd54eea
docs: update Yarn FAQ
ba79c85
docs: typos. clarifications
75778bc
docs: troubleshooting
d6c398f
docs: add heading anchor
fdb995f
docs: publish with gitbook
ed89361
docs: documentation improvements
f4d9ebe
fix(security): Updated marked dependency
5bc46a0
feat: allow to release from local machine
There are 21 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: