Closed greenkeeper[bot] closed 6 years ago
Merging #270 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #270 +/- ##
=======================================
Coverage 71.14% 71.14%
=======================================
Files 63 63
Lines 1019 1019
Branches 181 178 -3
=======================================
Hits 725 725
Misses 292 292
Partials 2 2
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update dcfad7d...30d828e. Read the comment docs.
Update to this version instead π
The new version differs by 10 commits.
b2d82c2
docs: specify for each step if one or more plugins are required/allowed
31ec1eb
docs: fix configuration doc syntax
d8c84a0
fix: clarify EPLUGINCONF
error message
3cc62f0
docs: add JS API documentation
417779e
feat: return lastRelease
, commits
, nextRelease
, releases
from JS API
c574435
refactor: pass complete context
to lib/plugins/normalize.js
0626d57
feat: log with signale
and allow to customize stdin
and stdout
f64046f
docs: fix link to resources page
1d4f67e
test: use semanticrelease/npm-registry-docker
Docker image for tests
b9af5c4
docs: add new semantic-release-gcr plugin link
See the full diff
Version 15.7.2 of semantic-release was just published.
The version 15.7.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
v15.7.215.7.2 (2018-07-16)
Bug Fixes
Commits
The new version differs by 34 commits.
d3c7232
fix(package): update git-url-parse to version 10.0.1
89e5847
docs: migration to new GitBook version
ed6a381
chore(package): update clear-module to version 3.0.0
d8e59cc
fix: set default path to
generateNotes
object config24ce560
refactor: build plugin pipeline parameters at initialization
eb26254
refactor: use
Object.entries
rather thanObject.keys
50061bb
refactor: remove unnecessary object destructuring
5989989
feat: allow to define multiple
generateNotes
plugins576eb60
refactor: simplify plugin validation
f7f4aab
refactor: use the
lastInput
arg to compute theprepare
pipeline next input12de628
refactor: fix incorrect comments in
lib/plugins/pipeline.js
d303286
docs: fix default value for
analyzeCommits
plugined9c456
refactor: always return an
Array
of results/errors from a plugin pipelinecac4882
docs: clarify
verifyRelease
plugin description09348f1
style: disable
max-params
warning forlib/plugins/normalize.js
There are 34 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: