Open greenkeeper[bot] opened 6 years ago
Update to this version instead π
semantic-release
>= 15.9.0
devDependency
@semantic-release/npm was updated from 3.4.1
to 5.0.5
.Update to this version instead π
The new version differs by 6 commits.
df993c7
fix: use default value for null
options
124aca1
docs: harmonize docs with other plugins
98fc020
chore(package): update commitizen to version 3.0.0
ec20a08
chore(package): update nock to version 10.0.0
a1e46d6
chore(package): update xo to version 0.23.0
6e53a42
chore(package): update delay to version 4.0.0
See the full diff
devDependency
@semantic-release/npm was updated from 3.4.1
to 5.0.6
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.0
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.1
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.2
.Update to this version instead π
false
if the npm publish is skipped (45890fd)The new version differs by 7 commits.
45890fd
fix: return false
if the npm publish is skipped
bd16cfb
style: minor style change in lib/publish.js
0b1f93a
chore(package): update p-retry to version 3.0.0
c59e32a
chore(package): update nyc and sinon
92e3115
test: delete unnecessary test helper file
f028c87
refactor: remove unnecessary let
declaration
baf071b
docs: update semantic-release default branch in links
See the full diff
devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.7
.Update to this version instead π
The new version differs by 9 commits.
46ec5ee
fix(package): update aggregate-error to version 3.0.0
d03aff2
fix(package): update read-pkg to version 5.0.0
7a55e35
chore(package): update p-retry to version 4.0.0
982504a
chore(package): update get-stream to version 5.0.0
b72a989
chore(package): update ava to version 1.3.1
62b27c5
fix(package): update npm to version 6.8.0
9651b04
chore(package): update xo to version 0.24.0
d506b9a
fix(package): pin npm to 6.5.0
50c0d5e
test: update ava to version 1.0.1
See the full diff
devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.9
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.11
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.12
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.13
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.1.15
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.2.0
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.3.1
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.3.2
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.3.3
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.3.4
.devDependency
@semantic-release/npm was updated from 3.4.1
to 5.3.5
.devDependency
@semantic-release/npm was updated from 3.4.1
to 7.0.0
.devDependency
@semantic-release/npm was updated from 3.4.1
to 7.0.1
.devDependency
@semantic-release/npm was updated from 3.4.1
to 7.0.2
.devDependency
@semantic-release/npm was updated from 3.4.1
to 7.0.3
.devDependency
@semantic-release/npm was updated from 3.4.1
to 7.0.4
.devDependency
@semantic-release/npm was updated from 3.4.1
to 7.0.5
.
Version 4.0.0 of @semantic-release/npm was just published.
The version 4.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/npm.
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
v4.0.04.0.0 (2018-07-17)
Features
cwd
andenv
options passed by core (f2e30c7)BREAKING CHANGES
semantic-release
>=15.8.0
Commits
The new version differs by 1 commits.
f2e30c7
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: