coveralls
commented
7 years ago Coverage remained the same at 100.0% when pulling 132e24134a25d84beaba9d422c8bec44874bf451 on greenkeeper/jsonwebtoken-7.2.0 into 47467c4947ff8c74020eb13585f15d6e74f5fd2e on master.
Version 7.2.0 of jsonwebtoken just got published.
The version 7.2.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 jsonwebtoken. 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 10 commits .
3a8b2b67.2.0669268eMerge branch 'silvermanj7-patch-1'cb21185Merge branch 'patch-1' of https://github.com/silvermanj7/node-jsonwebtoken into silvermanj7-patch-1653db58Merge branch 'dominykas-latest-joi'99127eeMerge branch 'latest-joi' of https://github.com/dominykas/node-jsonwebtoken into dominykas-latest-joi2c54016Merge pull request #277 from skyzyx/masterb412be9Simpler PR which implements the changes from #249.3febcc1upgrade to latest nodes and Travis infrastructure715e3d9upgrade joiccc7610Restructured a sentenceSee 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: