Update semver to the latest version 🚀 #4044
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 5.4.1 just got published. |
Codecov Report
@@ Coverage Diff @@
## master #4044 +/- ##
==========================================
- Coverage 90.72% 90.72% -0.01%
==========================================
Files 116 116
Lines 7939 7937 -2
==========================================
- Hits 7203 7201 -2
Misses 736 736
Continue to review full report at Codecov.
|
acinader
approved these changes
Aug 29, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 5.4.0 of semver just got published.
The version 5.4.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 semver.
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 16 commits.
e1c49c8v5.4.03ebc11dmore test coverage5b30513speed up tests a lot, add coveragee1668ceadd top level intersects function6cb2bcbintersection: use semver.version, not semver.raw4bacbfaMake exposed apis more clear8b86a26Reduce line length and remove unused platform parameter99f133eAdd range and comparator intersection docs to READMEafbe8caMove methods to comparator and range67c9ed7Add support for range and comparators comparisoncaeeac4remove 0.x from Travis, cache npm stuff, use containersbdda1a4Add Node.js 8 to .travis.yml8fff305Add node 6 to travisaaba710Added syntax highlighting to readme example32802c5minimize heap allocations for maxSatisfying/minSatisfyingThere are 16 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴