Open greenkeeper[bot] opened 6 years ago
devDependency
@semantic-release/changelog was updated from 2.1.2
to 3.0.1
.Update to this version instead π
The new version differs by 5 commits.
92608a3
fix: use default value for null
options
1b291d8
docs: harmonize docs with other plugins
a1266a1
chore(package): update commitizen to version 3.0.0
1c39499
chore(package): update xo to version 0.23.0
63df33f
chore(package): update xo to version 0.22.0
See the full diff
devDependency
@semantic-release/changelog was updated from 2.1.2
to 3.0.2
.devDependency
@semantic-release/changelog was updated from 2.1.2
to 3.0.4
.Update to this version instead π
The new version differs by 6 commits.
50ed752
fix(package): update fs-extra to version 8.0.0
dd0d91f
chore(package): update tempy to version 0.3.0
00204d2
chore(package): update nyc to version 14.0.0
50789ef
fix(package): update aggregate-error to version 3.0.0
cb9c5eb
chore(package): update xo to version 0.24.0
7474f2c
chore(package): update ava to version 1.0.1
See the full diff
devDependency
@semantic-release/changelog was updated from 2.1.2
to 3.0.5
.devDependency
@semantic-release/changelog was updated from 2.1.2
to 3.0.6
.devDependency
@semantic-release/changelog was updated from 2.1.2
to 5.0.0
.devDependency
@semantic-release/changelog was updated from 2.1.2
to 5.0.1
.
Version 3.0.0 of @semantic-release/changelog was just published.
The version 3.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/changelog.
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
v3.0.03.0.0 (2018-07-17)
Features
cwd
andenv
options passed by core (3173a68)BREAKING CHANGES
semantic-release
>=15.8.0
Commits
The new version differs by 1 commits.
3173a68
feat: use
cwd
andenv
options passed by coreSee 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: