This repository has been archived by the owner on Apr 29, 2020. It is now read-only.
Update jsonwebtoken to the latest version 馃殌 #117
Conversation
This file contains 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}
Codecov Report
@@ Coverage Diff @@
## master #117 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 14 14
Lines 168 168
Branches 11 11
=====================================
Hits 168 168Continue to review full report at Codecov.
|
Version 7.4.3 just got published.Update to this version instead 馃殌 CommitsThe new version differs by 6 commits.
See the full diff |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 7.4.2 of jsonwebtoken just got published.
The version 7.4.2 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 12 commits.
e56f904update changelog480bb9b7.4.2c6a7026Merge pull request #374 from ziluvatar/add-check-for-empty-secretsc584d1csign: add check to be sure secret has a value43739dcMerge pull request #371 from ziluvatar/docs-about-refreshing-tokens016fc10docs: about refreshing tokens5f44a86Merge pull request #365 from ziluvatar/information-regarding-base64-secretsc25e990docs: verifying with base64 encoded secrets2f36063Merge pull request #360 from ziluvatar/add-ecdsa-tests00086c2document keyid as option (#361)89900eaAdd tests for ES25627a7f1dreadme: Using private key with passpharase (#353)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 馃尨