This repository was archived by the owner on Apr 29, 2020. It is now read-only.
Update passport-jwt to the latest version 🚀#119
Open
greenkeeper[bot] wants to merge 1 commit intomasterfrom
Open
Update passport-jwt to the latest version 🚀#119greenkeeper[bot] wants to merge 1 commit intomasterfrom
greenkeeper[bot] wants to merge 1 commit intomasterfrom
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
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 3.0.0 of passport-jwt just got published.
The version 3.0.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 passport-jwt.
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 30 commits.
28ffbb0Update package versioncfa4db3Merge branch 'pr108-secret-key-provider'3a07c77Update docs for 2.x.x to 3.0.0 migrationd5af311Get rid of JWT as the default auth scheme.80e049cTravis docs don't specifically mention v8ef0cecdAdd test to cover missed branch in strategy.1bb3d5bshould be clear that jwt passed to secretOrKeyProvider is not decodeda236e40Cleanup of PR #108.b3846efMerge branch 'secret-key-provider' of https://github.com/gpoole/passport-jwt into pr108-secret-key-provider98a7a09Merge branch 'pr-113-jwtOptions'4a7416cMerge branch 'master' of https://github.com/itayadler/passport-jwt into pr-113-jwtOptionsc1dccf8Merge branch 'pr-118-case-insensitive-auth-scheme'd127fd8Calculate auth_scheme.toLowerCase() onceb1d7cccTest for case insensitive comparison of token_type39af785changed scheme comparison to be case insensitiveThere are 30 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 🌴