The version 4.0.0 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 standard-version.
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.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling a7bf8e39a34bf87380b93d721f12bf55d9eb8daf on greenkeeper/standard-version-4.0.0 into 959d5ee42d3e683020f8710a29ca6f893a388c99 on master.
Coverage remained the same at 100.0% when pulling a7bf8e39a34bf87380b93d721f12bf55d9eb8daf on greenkeeper/standard-version-4.0.0 into 959d5ee42d3e683020f8710a29ca6f893a388c99 on master.
Coverage remained the same at 100.0% when pulling a7bf8e39a34bf87380b93d721f12bf55d9eb8daf on greenkeeper/standard-version-4.0.0 into 959d5ee42d3e683020f8710a29ca6f893a388c99 on master.
Version 4.0.0 of standard-version just got published.
The version 4.0.0 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 standard-version. 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.
Commits
The new version differs by 20 commits .
0d8be31
docs: remove 4.0.0-1 from CHANGELOG
5bd97f2
chore(release): 4.0.0
bd12e00
docs: remove 4.0.0-0 from CHANGELOG
5f529a9
chore(release): 4.0.0-1
af9597d
docs: slight nit regarding command description
2894bbc
fix: should print message before we bump version
b788c5f
feat: add support for bumping version # in bower.json (#148)
70b20c8
feat: make tag prefix configurable (#143)
5c543a1
Revert "Add: bower support" (#147)
219df9b
Add: bower support (#134)
a513fa2
chore(release): 4.0.0-0
e560cd3
docs: a few documentation nits (#145)
068008d
feat: support releasing a custom version, including pre-releases (#129)
b6e1562
fix: include merge commits in the changelog (#139)
b747feb
chore(package): update nyc to version 10.0.0 (#144)
There are 20 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: