🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of semantic-release.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage increased (+0.02%) to 98.002% when pulling cdabd160a9cc05957eab785025745aaae330faee on greenkeeper-semantic-release-6.3.6 into 53f0beec9ad9a33a9f6b47649ca34a4d6bae95f8 on master.
Coverage increased (+0.02%) to 98.002% when pulling cdabd160a9cc05957eab785025745aaae330faee on greenkeeper-semantic-release-6.3.6 into 53f0beec9ad9a33a9f6b47649ca34a4d6bae95f8 on master.
Hello lovely humans,
semantic-release just published its new version 6.3.6.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of semantic-release. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
<a name"6.3.6">
6.3.6 (2017-01-13)
Bug Fixes
The new version differs by 129 commits (ahead by 129, behind by 18).
af90de9
Merge pull request #355 from semantic-release/dep-updates
aa012b3
Merge branch 'greenkeeper/tap-9.0.0' into dep-updates
5724b19
Merge branch 'greenkeeper/github-8.0.0' into dep-updates
97a8e73
Merge branch 'caribou' into greenkeeper/nopt-4.0.0
51e12a3
docs(package): fix 'home' link
afd6ab7
fix(package): update github to version 8.0.0
f80e056
chore(package): update tap to version 9.0.0
b10c891
fix(package): update nopt to version 4.0.0
3295f95
fix(package): update github to version 7.0.0
6a172e1
docs(README.md): discourage use of pre-patch, pre-minor and pre-release
68f9753
chore(package): update dependencies
462c51d
style: standard
cdf705c
chore: update dependencies
9a51b02
chore: update github client
14618c8
chore(package): parse-github-repo-url
There are 129 commits in total. See the full diff.