Open greenkeeper[bot] opened 6 years ago
devDependency
semantic-release was updated from 8.2.3
to 15.9.16
.devDependency
semantic-release was updated from 8.2.3
to 15.9.17
.Update to this version instead 🚀
The new version differs by 5 commits.
9930dac
fix: add cwd
to ENOGITREPO
error message
bc8551c
fix: typo in EPLUGINCONF
error message
234a910
docs: add Waffle.io README badge
68fce96
chore(package): update commitizen to version 3.0.0
fb6e2d8
docs: add semantic-release-gerrit to plugins list
See the full diff
devDependency
semantic-release was updated from 8.2.3
to 15.10.3
.Update to this version instead 🚀
The new version differs by 11 commits.
0578c8b
fix: do not log outated branch error for missing permission cases
e291101
docs: add section existing tags in configuration docs
8853922
docs: add troubleshooting section for reference already exists
Git error
d45861b
docs: clarify the "npm missing permission" troubleshooting section
2ba0b81
docs: remove troubleshooting section related to legacy error messages
e93a663
docs: fix markdown link in configuration docs
58c25be
fix: fix logs for plugins loaded with plugins
option
ff275a5
fix: use module name in logs for plugins loaded with plugins
option
3e8216a
docs: typo in configuration docs
aa9d5c6
docs: add a Getting started
section and clarify config steps
5ba5010
feat: add new plugins
option
See the full diff
Version 11.0.2 of semantic-release was just published.
The version 11.0.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
v11.0.211.0.2 (2017-12-10)
Bug Fixes
Commits
The new version differs by 38 commits.
4053d8f
fix: log plugin type in addition of path
88f33ec
chore(package): update mockserver-client to version 5.1.1
0761ef3
style: update to prettier@1.9.0
f30fb6c
chore(package): update prettier to version 1.9.0
0113db2
docs(README): add node support policy
eec4e68
test: Isolate environment variables passed to semantic-release
8371a03
test: Verify
Error
instance type and SemanticReleaseError name2491032
test: Add test to check unexpected plugin return values
02ddf34
Fix: Remove redundant test of commitAnalyzer plugin output
6859591
chore: Clean up mistakenly added configs
613a646
fix: Typo in error messages
d7b323d
fix: Accept
undefined
values for thegetLastRelease
andgenerateNotes
pluginsa7359bf
test: Improve docker start/stop script
fcb832b
fix: remove
name
from log as it's not an existing option anymore89f5e07
chore(package): update ava to version 0.24.0
There are 38 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: