semver just published its new version 5.1.0, which is covered by your current version range. No automated tests are configured for this project.
This means it’s now unclear whether your software still works. Manually check if that’s still the case
and close this pull request – if it broke, use this branch to work on adaptions and fixes.
Do you think getting a pull request for every single new version of your dependencies is too noisy?
Configure continuous integration and you will only receive them when tests fail.
Hello :wave:
:warning::warning::warning:
semver just published its new version 5.1.0, which is covered by your current version range. No automated tests are configured for this project.
This means it’s now unclear whether your software still works. Manually check if that’s still the case and close this pull request – if it broke, use this branch to work on adaptions and fixes.
Do you think getting a pull request for every single new version of your dependencies is too noisy? Configure continuous integration and you will only receive them when tests fail.
Happy fixing and merging :palm_tree:
The new version differs by 6 commits .
8e33a30
v5.1.0
c3a1f41
Backus-Naur for ranges
8cac175
Remove excessively cute inspect methods
a4ef7bf
tap 2
c917629
Merge pull request #141 from pwang2/README-Fix
c2a3bff
Fix the wrong semver pre(release) beta example
See the full diff.
This pull request was created by greenkeeper.io. It keeps your software, up to date, all the time.
Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster :zap: