:icecream: Powerful software development experience and management. Enhancing @tc39 JS, @denoland and @nodejs, because we need a bit of magic. :sparkles: You can think of it as Cargo for the JavaScript ecosystem.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 25 commits .
1727ea8docs: remove repeated entries added to changelog
Coverage remained the same at 100.0% when pulling 9ba65cdc6bb65d1d2030996cf572e70303cd62a5 on greenkeeper-standard-version-3.0.0 into 5701584840647dbaae29539249ca26534477c47d on master.
Hello lovely humans,
standard-version just published its new version 3.0.0.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 25 commits .
1727ea8
docs: remove repeated entries added to changelog
db55c66
chore(release): 3.0.0
432a100
chore: added release npm script
a903f4d
feat: added support for commitAll option in CLI (#121)
0ee080f
chore(package): update yargs to version 6.0.0 (#117)
ce268d9
chore(package): update mocha to version 3.1.0 (#115)
832458a
docs(readme): add silent option example to code usage section
e68bd6b
test: add mocked error tests to achieve full test coverage
2a3fa61
feat(options): add --silent flag and option for squelching output
34a6a4e
feat: separate cli and defaults from base functionality
28ff65a
chore: package.json engines field >=4.0, drop Node 0.10 and 0.12
e544339
chore: add os, npm and editor related ignores to git (#113)
f7a4915
fix(err): don't fail on stderr output, but print the output to stderr (#110)
d5d5e9e
chore(editorconfig): add editorconfig (#112)
2ce4160
fix: check the private field in package.json(#102) (#103)
There are 25 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade